Restoring, RUU, official? - HTC Rezound

Just got my Rezound about a week ago, and this is the FIRST HTC Android phone I have ever had. First unlocked phone as well!
I have experience with Moto phones and the .sbf process and what not and am pretty good with adb, but still a noob.
Questions is, found this RUU from the dev section: RUU_Vigor_VERIZON_WWE_1.02.605.6_Radio_RS_0.95.00. 1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_22 1502_signed.exe
Is this the latest official RUU? I noticed by looking at the numbers vs my software version and it seems the baseband is off, so, If I flash this, this will return me to complete stock, will I be able to update my baseband via OTA Software update?
Thanks everyone.

You should be able to run the ruu on a pc and restore it to how it was out of the box. First you do have to re lock it though
sent from my newly unlocked Rezound

pwned3 said:
You should be able to run the ruu on a pc and restore it to how it was out of the box. First you do have to re lock it though
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
I know how to run it, just want to make sure that the ones posted are for one official and if the baseband is slightly off by a few versions if doing an OTA update will update it. The latest RUU that I can find (here on XDA) looks like it has a different baseband than what came on the phone.
And yes, re-locking before the RUU flash is a must.

Related

[Q] Bootloader Unlock not working

I downloaded the hBoot upgrade RUU, everything goes fine then it tell's me I'm not updated to the latest version... xx.xxx.406(?).xxx even though I am when I go to phone settings. I even downgraded by RUU and did an OTA to make sure it was HTC official and not rooted. Any ideas?
That program never worked for me... If you are rooted you can get an unlocked bootloader by flashing a package found here
Thanks very much.. it's such a shame as I really wanted to see what HTC had to offer. I didn't even need it much I had a custom recovery before and could do anything from there I jsut wanted to try stock

Used HTC Thunderbolt, Getting things set up

Okay, so I ordered a USED Thunderbolt on ebay last week and it should be here tomorrow. I'm not entirely new to rooting and such as I have a droid 2 global now, but that's motorola which seems to be fairly different from HTC. Anyway I've been reading threads and have come up with a few questions.
For instance if my phone is rooted when I get it, how can I get back to stock. I won't know how it was rooted, and some guides say it matters, while others don't. Plus many guides say not to just flash an RUU over a rooted phone, but if it replaces the bootloader, radio, and system, why not. Isn't that basically like an SBF on a motorola phone? Can I then also do a data wipe from the hboot bootloader thing on my phone and end up with a perfect stock device without any risk? From what I understand some roots block this entirely on the phone though so maybe I can't. I'm not really sure how to know what is safe to do on a phone that I didn't previously own and would love a guide to how to check these things and what to do so I don't brick the phone.
Also I can't seem to find a functional link to any of the latest radios, does anyone have a working link, and do people recommend the leaked radio from the most recent leaked build, or an official radio? and if so what radio is official? the one ending in 906 seems to be the most recent that I think is official but I'm not sure, though I am almost certain the 916 one isn't official, it appears to have been released in january on rootzwiki, while the most recent leaked build was less than a week ago from what I understand, but I don't know if it has a new radio or not.
Aside from that I think I've got it all down. figure out how to get phone to most recent stock OTA update. get 4g lte sim card, activate, root using this method.
http://rootzwiki.com/topic/20864-tool-root-2116059-and-19-no-downgrade-or-data-wipe/
then if I don't have the most recent radio I can flash it in the hboot thing, and can use cwm to flash any rom I want and a recommended kernel (I'm thinking thundershed 1.5 for starters though wouldn't mind some recommendations. I love Cyanogenmod)
Does this sound about right?
Also I'm not sure how hboot on htc phones works aside from booting on power+vol down button, but does the hboot allow for clearing data and cache as well as flashing things? On my droid 2 global there is a bootloader than can only be used to flash sbf files to get back to stock ota, and then there is a motorola stock recovery on the phone that is used for flashing updated ota updates that are signed or wiping data/cache. Are these the same on htc or are there a 2 different ones on that phone as well? I do understand that no PC is required for the htc as the tool to flash an ruu is built into the phone even if it is an older one than what the phone is currently on right?

[Q] RUU Failed

I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.

[Q] rezound OTA over usb help wanted

I have a Rezound that is not active. It just gets used around the house on wifi for checking email, facebook, and to control the wifi thermostat. I would like to get the latest OTA but cannot do it from the phone as it does not have an active sim. I don't really want to root the phone. I did the PH98IMG zip method to get 4.03.605.2 but it seams a little slow and it is my understanding that there is a new version of 4.05 or perhaps newer OTA... Does anyone have a link to a zip of the OTA that I can download?
Thanks for the help!
happyharvick said:
I have a Rezound that is not active. It just gets used around the house on wifi for checking email, facebook, and to control the wifi thermostat. I would like to get the latest OTA but cannot do it from the phone as it does not have an active sim. I don't really want to root the phone. I did the PH98IMG zip method to get 4.03.605.2 but it seams a little slow and it is my understanding that there is a new version of 4.05 or perhaps newer OTA... Does anyone have a link to a zip of the OTA that I can download?
Thanks for the help!
Click to expand...
Click to collapse
Well, your in a bad spot actually... 4.3.605.2 does not have an upgrade path at all, there is no OTA from it, or to it for that matter... it was an unofficial leaked firmware that is not supported in the standard software streams. Even if it was active on Verizon, it would never see an upgrade... ever.
You have 3 choices here:
1) S-OFF the device and get back to an official software build and manually OTA up (See the instructions for Full Downgrade/Upgrade here)
2) Assuming you are already Hboot unlocked, flash a custom ROM or a stock-ish ROM, there is a pre-rooted 4.5.605.14 ROM in the dev section
3) Stick with what you got, to be honest the ROM you have is pretty stable.
acejavelin said:
Well, your in a bad spot actually... 4.3.605.2 does not have an upgrade path at all, there is no OTA from it, or to it for that matter... it was an unofficial leaked firmware that is not supported in the standard software streams. Even if it was active on Verizon, it would never see an upgrade... ever.
You have 3 choices here:
1) S-OFF the device and get back to an official software build and manually OTA up (See the instructions for Full Downgrade/Upgrade here)
2) Assuming you are already Hboot unlocked, flash a custom ROM or a stock-ish ROM, there is a pre-rooted 4.5.605.14 ROM in the dev section
3) Stick with what you got, to be honest the ROM you have is pretty stable.
Click to expand...
Click to collapse
Thanks for taking the time to reply but I am not sure what you are referring to by "s-off" or hboot unlocked"
Can you point me in the right direction to learn a little more?
Thanks!
Hboot unlock is a process which is done via htcdev.com, it unlocks the phone to allow custom ROMs and recovery... Go to their site for more details or check out any of several YouTube videos.
S-Off is a means of turning off all security checks in the device, such as flashing an older RUU to downgrade. It is accomplished after Hboot unlock with a tool like RumRunner, check out rumrunner.us for more info.
If you are completely unfamiliar with unlocking, rooting, romming, or that kind of stuff, Google can be your friend here to learn the ins and outs, plus the sticky threads in the Rezound sections here.

"Unfortunately, AT&T Ready2Go has stopped." Is stuck looping on my phone.

"Unfortunately, AT&T Ready2Go has stopped." Is stuck looping on my phone.
About a year ago I rooted my phone, following these directions. (I can't yet post a link, but the first option on google when searching "how to root m8" is the site, htconeroot.com, that I used.)
This morning I noticed that my phone was not vibrating anymore no matter if I restarted the phone or what settings were applied. So I checked online to see if there was a fix, and a factory reset was recommended.
So when I got back from work today, I thought I had successfully uninstalled the root using SuperSU. Then I performed a factory reset. My phone then went into TWRP recovery which was alarming. So I rebooted the system from TWRP , then the message in the title kept popping up over and over again, so I am in a bit of a pickle. I can message and call at the moment but that is about it.
I'm thinking the problem is similar to this one someone had on a note 3, except I was trying to factory reset rather than update. http://forum.xda-developers.com/showthread.php?t=2663120
Has this happened to anyone else, and do you have any suggested fixes for resetting this phone???
Thanks in advance.
I've seen a number of cases on the M8 forums of various processes stopping with message "XXX has stopped" after a factory reset. Not sure what is causing this. But there are a variety of ways to recover.
Since you have TWRP, you can try to restore a TWRP backup of your own (if you made one) or install a stockish ROM. Those methods may be helpful if you want to retain or retrieve any personal data.
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
redpoint73 said:
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
Click to expand...
Click to collapse
Honestly I'd be fine returning to full stock, at least for the time being, to see if the vibration problem would fix itself. But do I need to be S-OFF for RUU?
eaflook said:
But do I need to be S-OFF for RUU?
Click to expand...
Click to collapse
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
redpoint73 said:
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
Click to expand...
Click to collapse
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
eaflook said:
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Click to expand...
Click to collapse
No, you're looking in the right place. Its somewhat common for OS number to be blank, its a known bug in older TWRP versions that it deletes the OS number.
What does it say for hboot number and radio number?
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
eaflook said:
U
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
Click to expand...
Click to collapse
You can do that. All that "guide" describes is one way to get a ROM on an SD and flash it, which is one of the options I already suggested in Post #2 above.
But what ROM will work, somewhat depends on the info I requested above.
redpoint73 said:
What does it say for hboot number and radio number?
Click to expand...
Click to collapse
hboot number-3.19.0.0000
radio [email protected]
redpoint73 said:
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
Click to expand...
Click to collapse
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
eaflook said:
hboot number-3.19.0.0000
radio [email protected]
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
Click to expand...
Click to collapse
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
eaflook said:
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
Click to expand...
Click to collapse
Good practice is to post what you did (or going to do) for the benefit of others that may have the same question; or so we can verify you are on the right track.
In case others may have the same question (or you get stuck again), all TWRP versions, and instructions (recommend install with fastboot method) are here: https://twrp.me/devices/htconem8gsm.html

Categories

Resources