Related
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
I have a rooted and S-on Evo. The RUU keeps failing, even after I unrooted via the Superuser app.
Keep getting “ERROR [155]: UNKNOWN ERROR” and then it says it can not update the phone.
And then “Please get the correct ROM update utility and try again.”
I am definitely using the correct RUU version. 1.22.651.3.
Also I have tried two different computers and two different USB cables.
Does anyone know how to get this thing working?
if you updated to the latest OTA update; that usually updates your radios and your Hboot which means the old RUU won't work because it has an OLDER HBoot and radios. Your gonna have to wait till the new OTA becomes available as an RUU to be able to go back to stock.
if you didn't take the OTA 2.13 and you are still on 1.22 then try putting your phone on Fastboot and try it that way.
Edit: Ok so it looks like the latest RUU has been uploaded. Look here http://www.filefactory.com/f/b6eb73c80cc97030/
Thanks, I will try fastboot.
However, as I said in the OP, I am on the same version (1.22.651.3) as the RUU I am using...
ronnienyc said:
I have a rooted and S-on Evo. The RUU keeps failing, even after I unrooted via the Superuser app.
Keep getting “ERROR [155]: UNKNOWN ERROR” and then it says it can not update the phone.
And then “Please get the correct ROM update utility and try again.”
I am definitely using the correct RUU version. 1.22.651.3.
Also I have tried two different computers and two different USB cables.
Does anyone know how to get this thing working?
Click to expand...
Click to collapse
I ran into the same error 155 issue.
I found the solution and it's quite simple. In the instructions to unroot, they forget to mention that you MUST relock your bootloader (instructions below). Once you relock it, then you can run the RUU for 1.22.651.3.....after that, take the stock OTA update.
http://www.theandroidsoul.com/how-to-re-lock-htc-one-x-bootloader/
It helps to have HTC Sync installed too
Sent from my EVO using Tapatalk 2
Is there another site with the new ruu?
Sent from my EVO using Tapatalk 2
running "fastboot oem lock" yields "waiting for device," and this stays on the screen forever. It doesn't work...
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Hypeo said:
It helps to have HTC Sync installed too
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Correct - this is an important step too. HTC Sync must be fully installed, drivers and all.
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
Congrats!
That's my plan, except I'm keeping the stock ROM. If you find a way to Root, let me know - I tried RegawMOD, but I could not get it to work
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Rxpert said:
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Click to expand...
Click to collapse
I suggest no OTA as well!
Rxpert said:
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Click to expand...
Click to collapse
That's not always true, and almost all new major releases come with a new hboot. In fact I can't remember any updates on my 0g evo, evo 3d, and evo LTE, that didn't come with a new hboot. The fact of the matter is, people that are s-on and hboot 1.15 won't be able to upgrade their radios and firmware unless they take the ota or run the ruu. This update makes the phone fly and is worth it.
On the other post, regaw mod does work with unlocking and installing twrp, you will have to install a rooted rom afterwards though because regaw mod fails at the rooting step.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
The fact of the matter is, people that are s-on and hboot 1.15 won't be able to upgrade their radios and firmware unless they take the ota or run the ruu. This update makes the phone fly and is worth it.
On the other post, regaw mod does work with unlocking and installing twrp, you will have to install a rooted rom afterwards though because regaw mod fails at the rooting step.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Sweet this is actually the point where I'm at. HTC Dev unlocked, s-on, hboot 1.15 and rocking twrp. I've been trying to parse through all of the numerous posts on a method to go ahead and install the ota updates. I actually believe I'm 2 down as I haven't updated ever and I got the phone @ launch. I recall reading somewhere that just going back to the stock recovery is a viable option if I want to go w/ the ota updates. I don't really have any interest in different ROMs (I scratch that itch w/ my evo 3d).
tl;dr Whats the least painful way to install the OTA updates post HTC Dev unlock, s-on, twrp recovery, and hboot 1.15?
I successfully installed Fresh Evo LTE 5.3.1 on my phone.
One of the suggestions is to update the Radio but I'm having a tough time doing that.
Here are my specs:
HBOOT 1.15.0000
S-ON
FreshEVO 5.3.1 ROM
I went to the link from the FreshEVO LTE 5.3.1 page to update the radio and have tried the following to install the Radio:
Attempt 1
Downloaded the Full Firmware zip file
Rename it "PJ75IMG"
Place it in the root of my SD card
Reboot into Bootloader
The PJ75IMG.zip file is detect but I only get 'Parsing PJ75IMG.zip' and then the Fastboot, Recovery, etc. options are displayed.
Attempt 2
From the same page where I downloaded the Full Firmware zip file, I also tried:
Download the Boot.img Only (signed) file
Flash it through the command prompt while in Fastboot ("fastboot flash boot boot.img")
Go into Bootloader
The PJ75IMG.zip is detected but still get the "Parsing..." message and nothing else happens.
Attempt 3
I have also tried going into my TWRP recovery and installing the Full Firmware zip AND the Radio 1.12.11.0809 Only.zip file but the installation fails.
Any pointers or a link to a video or a post would be much appreciated.
Thanks and sorry if this is a duplicate post but I really couldn't find any post that showed step-by-step process.
revert to stock and accept the ota, you can then fastboot recovery again and reflash. hboot 1.15 can not directly flash any firmware
edit: you may have to relock your hboot but ive seen users state they didnt. if you decide to relock the phone you will have to unlock the bootloader again to enable fastboot
om4 said:
The easiest way to update your firmware is to revert to stock and accept the ota, you can then fastboot recovery again and reflash
Click to expand...
Click to collapse
I don't have my stock backup anymore.
I've heard stuff about using RUU or something like that. Any quick guide on how to revert back to stock?
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Rxpert said:
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Click to expand...
Click to collapse
Thanks for the warning.
Since I'm pretty new to all this, I'll play it safe and stick to what I have.
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
The new radios aren't worth losing the possibility, no matter how small
Sent from my EVO using Tapatalk 2
True...
om4 said:
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
Click to expand...
Click to collapse
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
RamesisX said:
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
Click to expand...
Click to collapse
I havent yet done it myself but users have said they didnt need to relock, how ever as captain said there is no real need to update right now. If you decide to go ahead it would be a good idea to relock ( fastboot oem lock ) just to make sure, you can unlock afterwards. I neglect to mention this in my guide because most phones now are on 1.19 anyway and those still on 1.15 are holding out for soff
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Rxpert said:
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
RamesisX said:
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
Click to expand...
Click to collapse
there is no simpler method for relocking hboot, simply fastboot oem lock
om4 said:
there is no simpler method for relocking hboot, simply fastboot oem lock
Click to expand...
Click to collapse
Used that and it worked great.
Evo 4G LTE
h-boot 1.19, s-on, HTCDev unlocked
Hey everyone,
I rooted my trusty Evo3D back when the phone was new and the process was fresh, and I really haven't kept up on any firmware updates or anything of that sort, but actively flash new ROMs. I'm running into constant issues that nobody else seems to have, and I think it's because I have outdated radio firmware and HBOOT:
HBoot: 1.40.1000
Radio: 0.97.10.0530
S-OFF
Can anyone point me in the right direction on where to find the newest files? It looks like the newest HBOOT is 1.58, but I can't locate the file and the only tutorials I've seen involve a lot of downgrading, stuff I'm not sure I need to do. If anyone can provide me any help, that'd be awesome.
Thanks
SicBoy34 said:
Can anyone point me in the right direction on where to find the newest files? It looks like the newest HBOOT is 1.58, but I can't locate the file and the only tutorials I've seen involve a lot of downgrading, stuff I'm not sure I need to do. If anyone can provide me any help, that'd be awesome.
Thanks
Click to expand...
Click to collapse
Given that you are having issues, I highly recommend that you flash the Sprint ICS RUU to re-sync your phone at the stock level, then flash a custom hboot and recovery. There's no need to relock your bootloader and you won't lose S-OFF. That will get you on the latest firmware in the cleanest manner possible.
ramjet73
ramjet73 said:
Given that you are having issues, I highly recommend that you flash the Sprint ICS RUU to re-sync your phone at the stock level, then flash a custom hboot and recovery. There's no need to relock your bootloader and you won't lose S-OFF. That will get you on the latest firmware in the cleanest manner possible.
ramjet73
Click to expand...
Click to collapse
i know this is an old thread but Im in the same configuration as the guy in the beginning of this thread but my phone is running fine. My end goal is that I would like to update the radio and hboot and then install another updated rom but i, not sure of where to start, thanks!
garol said:
i know this is an old thread but Im in the same configuration as the guy in the beginning of this thread but my phone is running fine. My end goal is that I would like to update the radio and hboot and then install another updated rom but i, not sure of where to start, thanks!
Click to expand...
Click to collapse
So you are on the old 1.40 hboot? Revolutionary s-off?
As recommended, if you want to get on the latest, just run the most recent ruu which you can get here: https://copy.com/fHLxtYEcygfqOKGg
then take the latest ota after you've run the ruu. Note that the ruu will return you fully stock. Also, please don't do this if you aren't s-off yet (which I assume you are).
After the ruu and ota update, you will be on all the latest firmware. You will still have s-off and can then do anything from there.
Let me know if you gave any specific questions or goals, but ruu is probably the best method.
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app