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
Related
Is there anyway to reset the Rezound to the factory locked bootloader?
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment); here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/sho...uide to S-On to restore that too if you wish.
PhantasmRezound said:
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment) and have it handy; here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/showthread.php?p=22045045
Now make sure your bootloader is Locked before running the RUU. Check this and be certain; have to do a bit of extra work if it isn't, so please say you didn't Dev Unlock again after doing S-off lol. (I did this. Had to repeat the whole S-off process to achieve a "Locked" message ultimately. Not fun.)
Ok, after making sure bootloader is Locked... Running that RUU should put the stock hboot back on, verify that after the process. And remeber to turn USB Debugging back on in the stock ROM after running that RUU lol . Then proceed with the guide on the same computer you got all those Dev tools on from doing S-off.
Click to expand...
Click to collapse
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
LakerStar25 said:
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
PhantasmRezound said:
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
Click to expand...
Click to collapse
Cool I was just trying to help out lol.
Sent from my ICS Rezound
Search has failed me, I have a rezound that i rooted after unlocking the bootloader and using hansons toolkit..
What is the best way to get to stock so I can accept the ICS update and re root?
I am familiar with how to relock my bootloader..
Thank you all
PS I called verizon today because my rezound is a bit fishy with the charger wanting to replace it to under warranty , they no longer have them available and are shipping the Razr Maxx as a substitute...UGGGH.
Don't accept that Motorola garbage.... Less processor speed and terrible screen also less dev support. Oh and you don't need to get back to stock to get ics just flash the ics ota in bootloader
Sent from my ADR6425LVW using xda app-developers app
please forgive my ignorance how do I flash the over the air update on to my phone from the bootloader mode
mayhem like me said:
Search has failed me, I have a rezound that i rooted after unlocking the bootloader and using hansons toolkit..
What is the best way to get to stock so I can accept the ICS update and re root?
I am familiar with how to relock my bootloader..
Thank you all
PS I called verizon today because my rezound is a bit fishy with the charger wanting to replace it to under warranty , they no longer have them available and are shipping the Razr Maxx as a substitute...UGGGH.
Click to expand...
Click to collapse
I've created a guide for rooted users to install the official ICS over-the-air: https://docs.google.com/document/d/1tmlh4OnplVfBNSjSyXfTYIVGfyb9lgI6ABpfg7gHY44/edit
I'm also working on a guide to restore root after installing ICS. It's not too bad at all, it's just finding a simple guide that's the trick... For restoring root after ICS, you can see my response here, where I reference discussions where I asked the same questions: http://forum.xda-developers.com/showthread.php?t=1829484
mayhem like me said:
please forgive my ignorance how do I flash the over the air update on to my phone from the bootloader mode
Click to expand...
Click to collapse
Correct me if I'm wrong, but you wouldn't do that for the over the air update.
You would need to flash stock recovery (assuming you've flashed a custom recovery), and then they can install the update through Android, like normal.
The guide i posted takes you through this process, as i did it.
---------- Post added 14th August 2012 at 12:08 AM ---------- Previous post was 13th August 2012 at 11:59 PM ----------
mayhem like me said:
PS I called verizon today because my rezound is a bit fishy with the charger wanting to replace it to under warranty , they no longer have them available and are shipping the Razr Maxx as a substitute...UGGGH.
Click to expand...
Click to collapse
Oh, and if you flashed Clockwork Mod, this is likely causing your charging problems. This is why i used AR Recovery 3.15 instead.
You can either take the OTA update or install an RUU.
Both ways, you have to relocked your bootloader or S-OFF.
For the OTA, you should be stock everything.
Stock recovery and rom.
For an RUU, just make sure you are on a rom that matches your firmware.
Gingerbread ROM on Gingerbread firmware.
Sent from my NeoMax Rezound
I have amon ra and I was responding to the first answer, I will try your method, do I have to go stock first or will the first step in your guide put me back to stock recovery, then relock bootloader .
mayhem like me said:
I have amon ra and I was responding to the first answer, I will try your method, do I have to go stock first or will the first step in your guide put me back to stock recovery, then relock bootloader .
Click to expand...
Click to collapse
For the OTA, you need to be stock everything or it won't install. This is why I included instructions on how to revert back to stock recovery before trying the OTA.
You do not need to re-lock your hboot if you have S-OFF. What happens is that the OTA update re-locks the bootloader and you have to unlock it again if you want to play with your device (like, re-install AR Recovery). Or, if you have S-Off, you can install a different hboot that's already unlocked, and then you can flash custom recoveries, etc. But since messing with the hboot is very risky, I chose to re-unlock my hboot the HTC way after installing the OTA.
*important edit*
The OTA may have worked for me with an unlocked hboot because I was S-Off prior to updating. If you're not S-Off, you may indeed need to re-lock before updating.
However, it may be just as easy to get S-Off. It's actually very easy. I will make a very easy guide for this as well. Let me know, and I can help you through it. I'm not an expert, but it doesn't take an expert. The hardest part for me was just finding a good, uncomplicated guide - doesn't seem to be one at the moment, though there is a ton of info out there.
Anyway, let me know if you want help getting S-Off.
bloodymurderlive said:
For the OTA, you need to be stock everything or it won't install. This is why I included instructions on how to revert back to stock recovery before trying the OTA.
You do not need to re-lock your hboot if you have S-OFF. What happens is that the OTA update re-locks the bootloader and you have to unlock it again if you want to play with your device (like, re-install AR Recovery). Or, if you have S-Off, you can install a different hboot that's already unlocked, and then you can flash custom recoveries, etc. But since messing with the hboot is very risky, I chose to re-unlock my hboot the HTC way after installing the OTA.
*important edit*
The OTA may have worked for me with an unlocked hboot because I was S-Off prior to updating. If you're not S-Off, you may indeed need to re-lock before updating.
However, it may be just as easy to get S-Off. It's actually very easy. I will make a very easy guide for this as well. Let me know, and I can help you through it. I'm not an expert, but it doesn't take an expert. The hardest part for me was just finding a good, uncomplicated guide - doesn't seem to be one at the moment, though there is a ton of info out there.
Anyway, let me know if you want help getting S-Off.
Click to expand...
Click to collapse
Think I may have to try S off , tried to get back to stock and bootloader relocked but stock recovery would not flash,, unlocked again and restored from a backup through Amon ra
mayhem like me said:
Think I may have to try S off , tried to get back to stock and bootloader relocked but stock recovery would not flash,, unlocked again and restored from a backup through Amon ra
Click to expand...
Click to collapse
you need to be unlocked if you want to flash recoveries. You should have flashed the stock recovery and then relocked. (if I'm understanding what you did)
mayhem like me said:
Think I may have to try S off , tried to get back to stock and bootloader relocked but stock recovery would not flash,, unlocked again and restored from a backup through Amon ra
Click to expand...
Click to collapse
Here is my new guide for S-OFF: https://docs.google.com/document/d/1_kRxD5LtazP7vEnr9cDb3iHwWB1ZfJD_yn6xXo7d1bo/edit
It's really very easy - at least it was for me. Using the metronome audio file that I linked to, I was able to successfully complete the wire trick on my first try. It was cake when actually doing it.
Let me know if this helps.
topgun1953 said:
you need to be unlocked if you want to flash recoveries. You should have flashed the stock recovery and then relocked. (if I'm understanding what you did)
Click to expand...
Click to collapse
hmm I dont remember...lol will flashing stock recovery take away SU and bring me stock? running another nand back up now...
mayhem like me said:
hmm I dont remember...lol will flashing stock recovery take away SU and bring me stock? running another nand back up now...
Click to expand...
Click to collapse
Flashing a different recovery doesn't modify the rom.
Sent from my NeoMax Rezound
mayhem like me said:
hmm I dont remember...lol will flashing stock recovery take away SU and bring me stock? running another nand back up now...
Click to expand...
Click to collapse
Flashing a recovery won't affect root. The OTA will break root, but it's simple to restore. That's the easy part.
What I think you should do first is achieve S-OFF (you do not need to re-lock if you achieve S-OFF. It's easy, and it makes switching ROMs easier).
Then flash stock recovery.
Then accept OTA update(s).
Then unlock again (rather than mess with your bootloader).
Then flash superSU to restore root.
All per my instructions. I think they will make it easy as possible for you. The hardest thing, I think, is trying to find a step-by-step guide on all of this.
Just my opinion. There's a lot of info out there, but it's hard to sort through which steps you should choose to do, and when you should do them.
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
My 3G has been terrible since I got the phone, so I finally took it in to the sprint repair shop. They said before they can look at it I need to unroot and take the latest sprint update.
If I go stock and take the official OTA update, will I be able to achieve S-OFF and root again?
How do I go about going completely back to stock?
Thanks!
If you are s-off, flash the ruu.exe. Everything will go back to stock (ROM, recovery, etc), but you will remain s-off. I think you have to lock the bootloader first, but you don't need to be s-on.
Imagika FTW... with Tapatalk 2
Raillery said:
My 3G has been terrible since I got the phone, so I finally took it in to the sprint repair shop. They said before they can look at it I need to unroot and take the latest sprint update.
If I go stock and take the official OTA update, will I be able to achieve S-OFF and root again?
How do I go about going completely back to stock?
Thanks!
Click to expand...
Click to collapse
Hello,
I believe I can help you out with this. Are you s-off right now? If so, then all you have to do is download the latest ruu. It's easy. You can find it in the development section under stickies. If your s-on however you will need to run the ruu.exe on your pc which I believe you can find that file under the stickies. Now if your s-off, you can flash the ruu file by renaming it to PG86IMG in all caps and placing it on the root of your sdcard and booting into bootloader and flashing it from there. If you are going to turn s-off back to s-on you must do this immediately after you flash the ruu. Just go to fastboot on your computer with your phone in fastboot and type this command fastboot oem write securityflag 3. I believe that's the right command. Just make sure your hboot is stock and not modified or else you will brick your phone. And of course you can still achieve s-off and reroot after that. Ramjet wrote a very simple and easy guide that will help you step by step with the easiest way to get there. You can find his guide in the general discussion section. If you have any questions please do not hesitate to ask.
Please hit the thanks button if helped you in Anyway. Goodluck.
This ruu? The second one?
Raillery said:
This ruu? The second one?
Click to expand...
Click to collapse
Those are firmware .zip's that won't return everything to stock. I'd suggest that you download the 2.89.651.2 ICS RUU.exe from one of the links in this post and run it from Windows. Then you will be totally stock except for S-OFF and they shouldn't care about that. When you get the phone back you can just flash a custom recovery then root the stock ROM or flash a custom rooted ROM without having to worry about getting S-OFF again, unless they set it back to S-ON when it is serviced.
ramjet73
ramjet73 said:
Those are firmware .zip's that won't return everything to stock. I'd suggest that you download the 2.89.651.2 ICS RUU.exe from one of the links in this post and run it from Windows. Then you will be totally stock except for S-OFF and they shouldn't care about that. When you get the phone back you can just flash a custom recovery then root the stock ROM or flash a custom rooted ROM without having to worry about getting S-OFF again, unless they set it back to S-ON when it is serviced.
ramjet73
Click to expand...
Click to collapse
Do you have the link to the ruu that can be run through the phone? I keep getting error 155 unknown error.
EDIT: Nvm it worked, just had to manually rebooted to bootloader.
Raillery said:
Do you have the link to the ruu that can be run through the phone? I keep getting error 155 unknown error.
Click to expand...
Click to collapse
That error means you didn't lock the bootloader first. Use the fastboot command: fastboot oem lock. Then run the ruu.
Imagika FTW... with Tapatalk 2
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