I was pretty sure that I had screwed my EVO beyond my ability to recover it. It's pretty noob level stuff, but I haven't been root since my OG EVO - and things were simpler then. Using the WinDroid tool I was able to easily unlock, twrp, and superuser my phone. Moonshine failed 30 or 40 times, so I was not able to achieve S-OFF, but I flashed an AOSP rom anyway and poof - screwed up my phone. I spent the entire day in TWRP / fastboot /flashing stock **** to get my phone working again. At one point in the process I lost the ability to mount usb so I was particularly screwed at that point. I eventually gave in and formated sdcard, then was able to push a stock rom, flashed that a few times, and also a superuser.zip and eventually I was back to running stock 3.17. I've learned something today - I think I'm better off just waiting until December when we get 4.3 and Sense 5 from HTC... Gah - what a day.
Anyway, thank you to the innumerable posts that pointed to the Don't Pank Q&A and elsewhere on the forums. Searching + reading = solution, most of the time. Also, if you (noob to semi-noob) have already OTA updated to 3.17 don't try to S-OFF until a developer has solved this problem, because you are (probably) going to screw it up (and fail).
:good:
SimianJones said:
I was pretty sure that I had screwed my EVO beyond my ability to recover it. It's pretty noob level stuff, but I haven't been root since my OG EVO - and things were simpler then. Using the WinDroid tool I was able to easily unlock, twrp, and superuser my phone. Moonshine failed 30 or 40 times, so I was not able to achieve S-OFF, but I flashed an AOSP rom anyway and poof - screwed up my phone. I spent the entire day in TWRP / fastboot /flashing stock **** to get my phone working again. At one point in the process I lost the ability to mount usb so I was particularly screwed at that point. I eventually gave in and formated sdcard, then was able to push a stock rom, flashed that a few times, and also a superuser.zip and eventually I was back to running stock 3.17. I've learned something today - I think I'm better off just waiting until December when we get 4.3 and Sense 5 from HTC... Gah - what a day.
Anyway, thank you to the innumerable posts that pointed to the Don't Pank Q&A and elsewhere on the forums. Searching + reading = solution, most of the time. Also, if you (noob to semi-noob) have already OTA updated to 3.17 don't try to S-OFF until a developer has solved this problem, because you are (probably) going to screw it up (and fail).
Click to expand...
Click to collapse
Has anyone on 3.17 tried DirtyRacun + BabyRacun for S-OFF? Everyone is saying Moonshine doesn't work, but if BabyRacun works, S-OFF would still be possible using any of the 3 existing methods.
Captain_Throwback said:
Has anyone on 3.17 tried DirtyRacun + BabyRacun for S-OFF? Everyone is saying Moonshine doesn't work, but if BabyRacun works, S-OFF would still be possible using any of the 3 existing methods.
Click to expand...
Click to collapse
Having thoroughly butt-fudged my phone last week, I am going to refrain from experimenting (at least until after I take comps in January).
SimianJones said:
Having thoroughly butt-fudged my phone last week, I am going to refrain from experimenting (at least until after I take comps in January).
Click to expand...
Click to collapse
Maybe if I get bored, I'll experiment with it.
And down the rabbit hole I go . . .
Got BabyRacun to work (after a hex edit to the file) to downgrade my mainver to 3.15.651.16, but the 3.15 RUU won't run. So . . .
I'm going to flash the 3.15 ROM manually through fastboot (boot.img & system.img) and then try DirtyRacun to see if it works. If that doesn't, I may try the 3.15 firmware package and see if that helps.
Alright, so here's where I am. I was able to downgrade my firmware successfully using the 3.16 extended firmware zip from Haus, and now it's just a matter of flashing 3.16 stock rooted so I can Moonshine. At least I proved it could be done, even if it wasn't easy. I believe Moonshine is going to be updated for it to work with 3.17 anyway, so this may have just been an opportunity for me to be reminded of all the crazy stuff I used to do to try and get S-OFF to work, lol.
Captain_Throwback said:
Alright, so here's where I am. I was able to downgrade my firmware successfully using the 3.16 extended firmware zip from Haus, and now it's just a matter of flashing 3.16 stock rooted so I can Moonshine. At least I proved it could be done, even if it wasn't easy. I believe Moonshine is going to be updated for it to work with 3.17 anyway, so this may have just been an opportunity for me to be reminded of all the crazy stuff I used to do to try and get S-OFF to work, lol.
Click to expand...
Click to collapse
But you still do not effectively have S-OFF with 3.17, right? I think you can flash the 3.17 radios separately, though, but I think there might be other stability fixes to sense that you would be lacking. Thanks for experimenting though.
JJW
SimianJones said:
But you still do not effectively have S-OFF with 3.17, right? I think you can flash the 3.17 radios separately, though, but I think there might be other stability fixes to sense that you would be lacking. Thanks for experimenting though.
JJW
Click to expand...
Click to collapse
Huh? Yes, I have S-OFF. What would I be lacking? I re-updated to the 3.17 firmware after S-OFF, and then flashed the 3.17 stock rooted. What fixes would I be missing?
At any rate, I'm running CM10.2 anyway.
Captain_Throwback said:
Huh? Yes, I have S-OFF. What would I be lacking? I re-updated to the 3.17 firmware after S-OFF, and then flashed the 3.17 stock rooted. What fixes would I be missing?
At any rate, I'm running CM10.2 anyway.
Click to expand...
Click to collapse
Ah, I thought that reflashing the 3.17 rooted stock rom would have pushed S-ON. Again thanks for looking at this.
SimianJones said:
Ah, I thought that reflashing the 3.17 rooted stock rom would have pushed S-ON. Again thanks for looking at this.
Click to expand...
Click to collapse
No, flashing a ROM won't put you back S-on. The fact is that Captain was able to find a way to downgrade from 3.17 S-on and still get S-off, which was the ultimate goal in his experiment. Much like back when people downgraded from Hboot 1.15 or 1.19 and used Lazy Panda to gain S-off prior to the Dirty Racun method being available.
Sent from my HTC EVO 4G LTE
Related
Forgive me for starting a new thread; I've utilized the search here and some Google-fu, but still have questions for the community.
I recently upgraded to an HTC Rezound from a Thunderbolt, and have accepted the stock OTA ICS update last weekend.
This has not stopped me from Rooting the device, however. Using an All-In-One Toolkit downloaded here, I was able to Unlock the Bootloader, Install custom Recovery (ClockWorkMod Touch), and have SU flashed. All signs point to root, but I would like to know a few things.
- Is there currently any method of acquiring S-OFF, other than the juopunutBear "Wire Trick"? It sounds incredibly risky, and I feel a bit hesitant to try it connecting pins on the back of my phone with insulated wire... I would like to have S-OFF, in case I want to roll back using a PH98IMG.zip
After rooting, I noticed that the text ****TAMPERED**** appears above the UNLOCKED line when I power on into HBOOT. Is this normal? Or have I messed things up? The best answer I have gleaned so far is from another device's forum, and that this simply indicates that I have root.
Would love to hear some feedback. This is my 5th Smartphone starting with the G1, and I have rooted every single one within days. Only the Rezound seems to be the trickiest for me.
Let me know your thoughts, thanks.
The hboot says tampered after you install a custom recovery so that's normal. I was the same way about s-off it seemed to risky and complicated but in all honesty it is very simple. It's our only way to get s-off and the main thing is getting the timing right for the wire trick. I got it on my second try. I would say just read up on it and gain as much info until you feel comfortable to do it.
Sent From My HTC Rezound
big_mike_2k6 said:
The hboot says tampered after you install a custom recovery so that's normal. I was the same way about s-off it seemed to risky and complicated but in all honesty it is very simple. It's our only way to get s-off and the main thing is getting the timing right for the wire trick. I got it on my second try. I would say just read up on it and gain as much info until you feel comfortable to do it.
Sent From My HTC Rezound
Click to expand...
Click to collapse
Thanks, that confirms a number of suspicions. & As I understand it, I need to be S-OFF in order to flash a custom ROM, correct?
And this is due to the fact that I not only have to flash the ROM in recovery, but also flash a Kernel through HBOOT?
I want to start flashing custom ROMs, but in the meantime, I'm fairly happy with rooted ICS. Got Google Now working, removed 'App Associations' menu, and removed the VZW crapware, so root is working out rather well
deadsoulboy said:
Thanks, that confirms a number of suspicions. & As I understand it, I need to be S-OFF in order to flash a custom ROM, correct?
And this is due to the fact that I not only have to flash the ROM in recovery, but also flash a Kernel through HBOOT?
I want to start flashing custom ROMs, but in the meantime, I'm fairly happy with rooted ICS. Got Google Now working, removed 'App Associations' menu, and removed the VZW crapware, so root is working out rather well
Click to expand...
Click to collapse
You don't need to be s-off to flash a Rom but you do need to flash the kernel separate in hboot when you're s-on. When you're s-off you don't have to. I myself usually stay fairly close to stock with a few tweaks here and there and of course Verizons crap long gone.
Sent From My HTC Rezound
One more thing... Given my software version, etc, if I S-OFF now, would I bork my device?
Also, it looks like at the unlimited.io site, there is only a Windows version of juopunutbear for Gingerbread, and early ICS versions. My phone's software is on version is 3.14.605.12; does this mean I should abandon attempting to S-OFF ?
deadsoulboy said:
One more thing... Given my software version, etc, if I S-OFF now, would I bork my device?
Also, it looks like at the unlimited.io site, there is only a Windows version of juopunutbear for Gingerbread, and early ICS versions. My phone's software is on version is 3.14.605.12; does this mean I should abandon attempting to S-OFF ?
Click to expand...
Click to collapse
No you'll be fine doing it on your current version. You can use the file from the unlimited.io site for the 3.14.605.05 ics leak it works with the official ics update.
Sent From My HTC Rezound
i know clockwork will bork your device im not sure if the touch version does the same thing.
I recommend installing Amon Ra recovery or TWRP.
If i helped thanks me
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
I have started searching and am having a hard time finding exactly what I need. Anyway, I haven't used my Rezound since I got my S3 so I am not really up to speed on where the Rezound is in terms of OTA updates and whatnot. Right now my Rezound is S-Off on a engineering hboot (I believe) and rooted, but it was stock otherwise (up until I stopped using it).
I would like to get it back to 100% stock (other than S-Off, I will leave that as is for now). What is the easiest way to get there? I am assuming flashing an RUU of the latest stock build? If so, what is the latest stock build that I would get if I re-activated the phone and updated it (meaning I don't want any leaks or anything).
Also, it has been so long since I did any flashing on the phone, but what is the easiest way to flash a RUU (since I have never done that). And can I just flash the latest RUU without flashing anything else first?
Thanks, and sorry for all of the noob questions.
xceebeex said:
I have started searching and am having a hard time finding exactly what I need. Anyway, I haven't used my Rezound since I got my S3 so I am not really up to speed on where the Rezound is in terms of OTA updates and whatnot. Right now my Rezound is S-Off on a engineering hboot (I believe) and rooted, but it was stock otherwise (up until I stopped using it).
I would like to get it back to 100% stock (other than S-Off, I will leave that as is for now). What is the easiest way to get there? I am assuming flashing an RUU of the latest stock build? If so, what is the latest stock build that I would get if I re-activated the phone and updated it (meaning I don't want any leaks or anything).
Also, it has been so long since I did any flashing on the phone, but what is the easiest way to flash a RUU (since I have never done that). And can I just flash the latest RUU without flashing anything else first?
Thanks, and sorry for all of the noob questions.
Click to expand...
Click to collapse
Find the lastest RUU. I know its on android police. Place the file on the root of your SD card, check md5, rename to ph98img.zip, boot into bootloader and let it do its thing. You should be up to date.
EDIT: for you http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
topgun1953 said:
Find the lastest RUU. I know its on android police. Place the file on the root of your SD card, check md5, rename to ph98img.zip, boot into bootloader and let it do its thing. You should be up to date.
Click to expand...
Click to collapse
Thanks! Yea, I just found it on android police. I am assuming it won't wipe the SD card or anything right? Since I am S-OFF I don't have to worry about re-locking correct?
Also, will that RUU get it back to the point where someone could get the OTA's and everything as if it was 100% stock with S-ON?
EDIT: How come that 4.03.605.2 isn't listed on HTC website yet? Has it not been pushed out yet? The one listed on their site is the 3.14.605.12
xceebeex said:
EDIT: How come that 4.03.605.2 isn't listed on HTC website yet? Has it not been pushed out yet? The one listed on their site is the 3.14.605.12
Click to expand...
Click to collapse
4.03.605.2 is the latest leak. it has changes to make the rezound a Verizon global phone.
3.14.605.12 is the last nationwide OTA official ICS.
HowardZ said:
4.03.605.2 is the latest leak. it has changes to make the rezound a Verizon global phone.
3.14.605.12 is the last nationwide OTA official ICS.
Click to expand...
Click to collapse
Ok thanks! So I think I want to stick with the 3.14.605.12 then since I am trying to sell the phone. So if I am Unlocked and S-OFF can I just flash the RUU or do I have to relock first? And do I need to flash the gingerbread firmware patch?
s-off and unlocked is fine to ruu.
---------- Post added at 10:30 AM ---------- Previous post was at 10:28 AM ----------
s-off and unlocked is fine to ruu.
no patch needed
HowardZ said:
s-off and unlocked is fine to ruu.
Click to expand...
Click to collapse
Awesome, thanks! It won't wipe the SD card I am assuming right? Just the phone?
xceebeex said:
Awesome, thanks! It won't wipe the SD card I am assuming right? Just the phone?
Click to expand...
Click to collapse
my experience is it wipes the internal sd, but left the removable microSD card untouched.
HowardZ said:
my experience is it wipes the internal sd, but left the removable microSD card untouched.
Click to expand...
Click to collapse
Ok cool. That is what I would assume would happen. The only other question is if I need the GB firmware patch as well or does the RUU take care of everything?
Thanks for your help!
It takes care of everything
Sent from my ADR6425LVW using Tapatalk 2
mjones73 said:
It takes care of everything
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks everyone!
EDIT: Will it also stay "Locked" and S-OFF?
xceebeex said:
Thanks everyone!
EDIT: Will it also stay "Locked" and S-OFF?
Click to expand...
Click to collapse
Yes , running the RUU will not effect s-off status nor your bootloader locked status.
not to hijack the thread....but I have a question that relates to getting back to stock. I am running business sense, with the OTA. I would like to get the other global OTA.. I am s on. How do I go about doing that?
flash stock recovery
relock
run which RUU? the newest one is a PH file on android police
unlock
flash amon ra
flash new rom
does that sound right?
the part that I am questioning is the fact the global RUU is a PH file. But it says I have to be completly back to stock and locked.
any help would be greatly appreciated
Thanks
putney1477 said:
not to hijack the thread....but I have a question that relates to getting back to stock. I am running business sense, with the OTA. I would like to get the other global OTA.. I am s on. How do I go about doing that?
flash stock recovery
relock
run which RUU? the newest one is a PH file on android police
unlock
flash amon ra
flash new rom
does that sound right?
the part that I am questioning is the fact the global RUU is a PH file. But it says I have to be completly back to stock and locked.
any help would be greatly appreciated
Thanks
Click to expand...
Click to collapse
I not sure about s on but I think you have to stock recovery and locke the hboot then runn the ruu on hboot
This is the latest one
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Why don't you s off before updating?
Kratz17 said:
I not sure about s on but I think you have to stock recovery and locke the hboot then runn the ruu on hboot
This is the latest one
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Why don't you s off before updating?
Click to expand...
Click to collapse
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
putney1477 said:
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
Click to expand...
Click to collapse
Ok I understand but whenever you decide to do it follow this guide its pretty easy.
http://forum.xda-developers.com/showthread.php?t=1696394
It says to be on a certain firmware but I have heard from other users that it's works with any ics firmware. Good Luck
putney1477 said:
I tried to get s off a few months ago.....I could not get it to work. the 2 doff Hboot things scared me.
I would really like to do it. But I need my phone for work, I am on call most nights. I am looking into getting a used smartphone just so that I can use that while trying to get s off.
thanks
Click to expand...
Click to collapse
I did s-off procedure a few months ago. it took several hours and kept failing. I used a large insulated paperclip with the insulating material removed from each end for good electrical contact.
What I had been doing wrong was not keeping the wire nice and straight in the hole. when the wire is not straight, it will not make good electrical contact with whatever is directly beneath the hole.
I just thought I'd share this tip in case it helps others.
regards,
Howard
p.s. There is no need to install the jbear modified hboot if you are uncomfortably with it. Installing the modified hboot is optional at the end of the s-off procedure. You will still have benefits of s-off with a htcdev unlocked bootloader while using a stock unlocked hboot. For example one can flash kernels via fastboot flash command with a stock hboot. s-off and jbear modified hboot are two separate modifications to the phone.
HowardZ said:
p.s. There is no need to install the jbear modified hboot if you are uncomfortably with it. Installing the modified hboot is optional at the end of the s-off procedure. You will still have benefits of s-off with a htcdev unlocked bootloader while using a stock unlocked hboot. For example one can flash kernels via fastboot flash command with a stock hboot. s-off and jbear modified hboot are two separate modifications to the phone.
Click to expand...
Click to collapse
actually, on a stock, locked HBoot, you CAN'T use any fastboot commands. That's why it's highly recommended to install the JBear HBoot, plus it gives you an easy option to do it and it does it without the user having to do anything
Listen up people, there seems to be an epidemic going on in the EVO LTE forums and it's called the Jelly Bean RUU. There are now at least 10 people on these forums that have tried to flash the latest ruu in an attempt to upgrade their phone to Jelly Bean from ICS. This method has totally [email protected]#ed up their phones. The ones that have done this have ended up with hboot 2.09 and that's it. The radios, firmware, and rom remain on what ever they were before the attempt and no way to re-flash. All subsequent attempts at fixing this situation fail. If you want to upgrade, the proper way to do this is re-lock your phone and take the ota, do not run the ruu. There are at least 3 threads from people with this problem and several posts in other threads asking for help. Don't become the next victim.
Sent from my A500 using Tapatalk
cruise350 said:
Listen up people, there seems to be an epidemic going on in the EVO LTE forums and it's called the Jelly Bean RUU. There are now at least 10 people on these forums that have tried to flash the latest ruu in an attempt to upgrade their phone to Jelly Bean from ICS. This method has totally [email protected]#ed up their phones. The ones that have done this have ended up with hboot 2.09 and that's it. The radios, firmware, and rom remain on what ever they were before the attempt and no way to re-flash. All subsequent attempts at fixing this situation fail. If you want to upgrade, the proper way to do this is re-lock your phone and take the ota, do not run the ruu. There are at least 3 threads from people with this problem and several posts in other threads asking for help. Don't become the next victim.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Wish I'd seen this sooner. I got hit too.
There is a possible fix found here http://forum.xda-developers.com/showthread.php?t=2097150
bigdaddy619 said:
There is a possible fix found here http://forum.xda-developers.com/showthread.php?t=2097150
Click to expand...
Click to collapse
I did the relock method but im stock on hboot screen? Any ideas?
lexcoupe2100 said:
I did the relock method but im stock on hboot screen? Any ideas?
Click to expand...
Click to collapse
Have you tried to fastboot unlock again using HTC dev.com? If you can, do that, then fastboot a recovery, then installed a rooted rom...I believe that may work, its been a while. Also for those wanting to upgrade from ICS to JB with full firmware, just install a JB rom and then download firmware for 3.15. I did so and ended up with hboot 2.09, updated radio, etc...or like said, s-off and take the ota.
Sent from my EVO using xda app-developers app
So, I totally effed up, and then found this thread after the fact... (facepalm...) I had originally ran the 3.15 RUU, and then proceeded to keep updating MeanBean, all the way through the rebase to 3.16. So now, I've ended up with:
S-ON
MeanBean 3.07
HBOOT 2.09.0000
RADIO 1.12.11.0809
FIRMWARE 3.16.651.3
PRI Version 2.45_003
I'm guessing this isn't supposed to look like this, because everyone else has Radio 1.12.11.1210 with the new 3.16 firmware... My plan was to relock, flash a stock rom, take the OTA, then unlock again.... But, I figured i'd come here and ask if this was a bad idea, if it would brick my phone, or if anyone had a better suggestion... Any thoughts?
I would get S-off, then flash the 3.16 update. Screw all the locking, unlocking and re-rooting
The advice is free....the bandwidth, not so much
FinZ28 said:
I would get S-off, then flash the 3.16 update. Screw all the locking, unlocking and re-rooting
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
I didn't realize i could safely S-off with the new HBOOT.... It would seem my fingers have been far from the pulse of the xda community lately... Thank you for the info, I will go do some research..
Mockingbird946 said:
I didn't realize i could safely S-off with the new HBOOT.... It would seem my fingers have been far from the pulse of the xda community lately... Thank you for the info, I will go do some research..
Click to expand...
Click to collapse
Yep. Dirty Racun and Facepalm both work with the new Hboot.
The advice is free....the bandwidth, not so much
FinZ28 said:
Yep. Dirty Racun and Facepalm both work with the new Hboot.
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
I'm thinking about buying another Evo just to try FacePalm hahaha
Sent from my PoS MoPho
I'm thinking about buying another Evo just to try FacePalm hahaha
Sent from my PoS MoPho
Click to expand...
Click to collapse
I have a coworker who wants me to root his LTE. I might try it then, assuming he ever gets the phone to me
The advice is free....the bandwidth, not so much
Will it help?
I'm s-off, and I'm having RIDICULOUS issues with the phone boot-looping right now. The only time I get past the boot animation is when I run the most recent CM nightly, and even then I only get to the wifi screen before it reboots. Do you think flashing the RUU again will help? I'm willing to go all the way back to near-stock (except for losing S-Off), so anything that'll help I'll try.
Thanks!
I wouldn't RUU due to bootloops. What recovery version are you using? Maybe it's just not wiping well.
From my Evo LTE, yup.
RE:
scottspa74 said:
I wouldn't RUU due to bootloops. What recovery version are you using? Maybe it's just not wiping well.
From my Evo LTE, yup.
Click to expand...
Click to collapse
I'm using TWRP 2.4 and I'm doing a full wipe every time (reset, system, both caches). Am I missing something? I cannot, for the life of me, figure out what the deal is. No other ROMs I've flashed even make it past the boot animation. I figured it must be the kernel, so I went back to CM. It get farther, but locks and reboots when setup tries to turn on Wifi.
Any thoughts?
Edit: thinking about downgrading TWRP. What say you?
I would try downgrading TWRP. 2.3.3 or 2.3.1 seem to be the most stable. Unless you have the new tp IMG, I think you need the latest TWRP if you do, (I could be wrong, I don't follow either too closely, as I always use older proven firmware and recovery). That's said, if S-off , tp can be downgraded.
From my Evo LTE, yup.
scottspa74 said:
I would try downgrading TWRP. 2.3.3 or 2.3.1 seem to be the most stable. Unless you have the new tp IMG, I think you need the latest TWRP if you do, (I could be wrong, I don't follow either too closely, as I always use older proven firmware and recovery). That's said, if S-off , tp can be downgraded.
From my Evo LTE, yup.
Click to expand...
Click to collapse
I downgraded to 2.3.3, wiped, ran the Superwipe .zip, and reflashed the CM nightly. I got as far as the homescreen (after I skipped setting up wifi and a Google account) before it locked and rebooted. I really think something is making the data and/or wifi receiver (whatever that part or parts may be) to get too hot, and the phone resets as a safety measure (maybe?). Could this be a kernel issue?
I've tried posting in the help forum to no avail. I would really rather be using my EVO than my Opti S, but I guess the good news is that I'm not out of luck (for service) completely. I REALLY hope it's not a hardware thing.
I had no problem doing the 3.15 RUU to get s-off. Downgraded touchpanel after to flash decks 3.4 had serious lag about a week later. Flashed bk to meanbean 3.09
Sent from my EVO using Tapatalk 2
I created a similar thread the other day but it got so overwhelming and it was just confusing me more so I deleted it. I'm starting a fresh one so I can maybe explain myself better, not confuse anyone else and get better answers.
I just got a replacement Rezound in the mail today. My phone is currently on 4.05.605.14 710RD, LOCKED, HBOOT is 2.28.0000 & radios are 2.23.10.0123r/2.23.10.0124r.
That last time I was able to S-OFF I used the wire method and ControlBear for Windows. I went to the website Unlimited.IO and they no longer support Windows so I have no idea on how to S-OFF since I did it months ago. However, I did find ControlBear v0.1 for Windows here on the forums: http://forum.xda-developers.com/showpost.php?p=27764982&postcount=2079 My first question is will this version work for me? If you download it and open it you can see the zips contents. I wasn't sure If had to RUU back down to an earlier version for it to work? And last time I ended up being on a Juopunutbear HBOOT somehow.
So basically I want to be able to get back onto CyanogenMod 10.1 properly this time. I haven't done anything to my phone yet, still unrooted, on stock, etc.. I know my first step is too unlock it using the htcdev website but from there I'm confused, I can't remember the steps its been too long.
I need someone to please explain how I can get back to CM 10.1 and remain on the latest firmware/drivers/hboot etc. So I need help with rooting, s-off, how to get TWRP recovery back on, which to do first, etc.
I appreciate the help and I'll make sure I save this in case it ever happens again. Also, my apologies again for the previous thread, it was just too much going on, I just need simple steps.
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
xanda143 said:
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
ControlBear 0.1 worked for me on Windows, took a few tries but it finally pulled through. These where my steps:
1. unlocked
2. flashed recovery
3. flashed [ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
4. flashed boot.img from the rom
5. did wired trick with CB 0.1
so i think im good now? just have a couple questions.
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
xXezmacXx said:
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
Click to expand...
Click to collapse
That's normal if you're still using an unpatched hboot. If you will still use some fastboot commands (I use fastboot boot zImage/fastboot flash zimage zImage alot) then look into vynlfreak's 2.27 patched hboot. DO NOT UNLOCK flash patched hboot instead.
xXezmacXx said:
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
Click to expand...
Click to collapse
Flash your rom and don't worry about mainver.
Just wanted to thank you two. I have always been hesitant about s-offing my phone. But seeing it here in a few simple steps gave me the courage to finally pull the trigger. I know I am super late to the S-Off party, but am thrilled to finally have arrived!