Related
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
antiseen said:
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
Just s-off on GB. You can do it on ICS or GB works the same way. Just if you RUU to ICS you will have to reunlock to soff.
Once s-off he can flash any ruu he wants in any order and keep s-off.
Also on a secondary note, you must have not had a thunderbolt when we first got s-off as getting s-off manually took about 30+ mins of constant cmd line use.
S-off on the rezound is much easier than it sounds. The only part that gives people trouble is the wire trick and mainly because it is all about timing.
Sent from my ADR6425LVW using XDA
I will say this outright: you can S-off right now using the GB package option on unlimited.io since that is the firmware you have. Answering the rest of this assuming an upgrade to ICS firmware, but that is the simplest path.
antiseen said:
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms).
Click to expand...
Click to collapse
Correct. If you're patching the firmware is still Gingerbread. Check in the bootloader for "hboot 2.11" to confirm this. Only way you can update firmware and radios while S-on is to run a RUU.
antiseen said:
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
Click to expand...
Click to collapse
When a phone gets an OTA update, it is expecting you to be on the latest official release. That currently is the 2.01.605.11 Gingerbread build, the first OTA we had. That means you need to be on the GB firmware, and stock everything else, not on ICS firmware.
That said, last part is correct: You would re-lock, flash an ICS RUU, unlock again, put recovery back on, and either flash a pre rooted stock ROM based on the leaks, or root the stock ROM yourself. Then you are on ICS firmware, ready for S-off.
antiseen said:
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
Click to expand...
Click to collapse
Leave the ROM. Do a nandroid backup. Re-lock and flash the RUU. You can restore the nandroid afterwards, just be sure to repatch the thing to new ICS firmware if you go that route. Check second listing in the Roll Up Sticky post in the Dev section.
antiseen said:
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
Unlimited.io has files for GB firmware and the first three out of four ICS leaks. Note this last leak, the fourth one, is compatible with the unlimited.io files for the third leak ("5/7 leak"). So little was changed, so you're safe going with that combo if you wish.
nosympathy said:
Also on a secondary note, you must have not had a thunderbolt when we first got s-off as getting s-off manually took about 30+ mins of constant cmd line use.
Click to expand...
Click to collapse
You're actually right. I didn't get my TB til June and I spent months reading how to get s-off and finally did it in...august or september, I forget. It was MUCH easier by then.
I was familiar with the original process(only by reading, but felt confident in doing it that way) but by the time I was done learning everything about it, revolutionary method came out and I did it that way.
I know that I can get s-off right now on his gingerbread firmware, my only question is what happens when ICS does get released and all the good ROMS start to come out? I want to get him on an AOSP rom when they come out. I feel like he'll be stuck on gingerbread firmware and when it comes time to flash any of the ICS roms, he'll be clueless. I could figure out how to do it if it required an extra step or two but explaining that to him might be a bit much. I'd rather him be geared for ICS (he has no intention of going back to gingerbread, ever).
Also, I was under the impression that flashing a RUU would make it S-on. So if I ever wanted to upgrade his firmware to ICS we would have to do the wire trick again to achieve s-off once more.
Anyway, Thanks a ton guys for your feedback already. Love this community and you're both a great help. Thanks for the clarification/instructions phantasm.
antiseen said:
I feel like he'll be stuck on gingerbread firmware and when it comes time to flash any of the ICS roms, he'll be clueless. I could figure out how to do it if it required an extra step or two but explaining that to him might be a bit much. I'd rather him be geared for ICS (he has no intention of going back to gingerbread, ever).
Click to expand...
Click to collapse
Hop through S-off with the GB files from unlimited.io. Keep the stock bootloader for now rather than flashing the JuopunutBear hboot when their program asks you. (Note S-off makes the bootloader "Locked" again, but the JB files are hacked so you can use them *as if* they are Unlocked status... handy and makes it simpler to get the phone ready for warranty exchanges again. But! We want to make sure we get ICS firmware and radios first...then slap on an *ICS* JB bootloader...)
antiseen said:
Also, I was under the impression that flashing a RUU would make it S-on. So if I ever wanted to upgrade his firmware to ICS we would have to do the wire trick again to achieve s-off once more.
Click to expand...
Click to collapse
Nope. Once you achieve S-off you keep S-off. The only thing that affects S-off is turning the flag back on manually yourself with some fastboot commands.
So now you will be S-off and with a Locked stock bootloader. Download the RUU from the 6/10 leak here, rename to just PH98IMG.zip and flash it in bootloader:
http://www.androidfilehost.com/main/-Support_Files-/RUU/Vigor/RUU_Vigor_3.14.605.10_PH98IMG.zip
Then grab "[ICS][2.25][JB][5-7]PH98IMG.zip" from SuperChilPil's repository. (Note the 6/10 leak and the 5/7 leak have the same bootloaders just like the first pair of leaks did, so this is fine to use.) Rename to PH98IMG.zip and flash in bootloader:
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
This will make you S-off with a JuopunutBear hacked hboot, running the latest firmware and ROM available. Choose a recovery to flash, preferably TWRP or AmonRa. ClockworkMod has charging issues, there is a fix floating around thanks to NilsP and his own source if you insist. You can then proceed to flash the ICS custom ROM of your choice.
TWRP:
http://forum.xda-developers.com/showthread.php?t=1613576
AmonRa:
http://forum.xda-developers.com/showthread.php?t=1339679
CWM (fixed):
http://forum.xda-developers.com/showthread.php?t=1722989
Edit: User zhp pilot claims this version of CWM is also not functioning properly at this time, see the thread. Proceed with caution on CWM.
And don't forget to make a splash screen now that you are S-off lol, stop blinding yourself with that white HTC screen:
http://forum.xda-developers.com/showthread.php?t=1615811
~~~
Other useful files for S-off if you don't have them on the PC... The latest HTC drivers (extracted from HTC Sync so you don't have to download all of that) and an adb/fastboot mini console:
https://rapidshare.com/files/1796700693/HTCDriver_3.0.0.021.exe
http://rapidlibrary.com/files/adb-fastboot-and-other-tools-zip_ulcmnmxxtci89on.html
antiseen said:
Anyway, Thanks a ton guys for your feedback already. Love this community and you're both a great help. Thanks for the clarification/instructions phantasm.
Click to expand...
Click to collapse
Nope, thanks you for asking.
antiseen said:
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
In order to S-off the Rezound, you need to be HTCDEVunlocked, Rooted and on Stock Rom.
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 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
Well guys im absolutely stumped. I bought a DNA off ebay in hopes of unbricking it and getting it back in business. My goal is to put STOCK VZW rom back on it. Im absolutely puzzled as to what im doing wrong here. The Phone will only boot in bootloader mode. It is recognized in ADB. (Please forgive me if im using wrong terminology) Ive downloaded the STOCK RUU. Once the device is plugged in and I open the RUU and get to the part where it ask me to update the image. Both fields are blank. There is nothing in either fields. When I click update ROM my computer just crashes and gets hung. As far as some additional info, My bootloader was UNLOCKED and is now relocked, has S-ON and HBOOT 1.33.0001. Any suggestions as to what im doing wrong. I just want a stock DNA back.
xbcustoms said:
Well guys im absolutely stumped. I bought a DNA off ebay in hopes of unbricking it and getting it back in business. My goal is to put STOCK VZW rom back on it. Im absolutely puzzled as to what im doing wrong here. The Phone will only boot in bootloader mode. It is recognized in ADB. (Please forgive me if im using wrong terminology) Ive downloaded the STOCK RUU. Once the device is plugged in and I open the RUU and get to the part where it ask me to update the image. Both fields are blank. There is nothing in either fields. When I click update ROM my computer just crashes and gets hung. As far as some additional info, My bootloader was UNLOCKED and is now relocked, has S-ON and HBOOT 1.33.0001. Any suggestions as to what im doing wrong. I just want a stock DNA back.
Click to expand...
Click to collapse
It appears that this has the ENG Boot on it, When it powers up it says something about being illegal to distribute outside of HTC, but then immediately goes into boot loader mode.
xbcustoms said:
It appears that this has the ENG Boot on it, When it powers up it says something about being illegal to distribute outside of HTC, but then immediately goes into boot loader mode.
Click to expand...
Click to collapse
That's not eng hboot. If it's s on it can't have eng hboot.
Sent from my HTC6435LVW using xda app-developers app
if it is unlocked flash twrp with fastboot and flash a rom from recovery.
xbcustoms said:
As far as some additional info, My bootloader was UNLOCKED and is now relocked, has S-ON and HBOOT 1.33.0001.
Click to expand...
Click to collapse
123421342 said:
if it is unlocked flash twrp with fastboot and flash a rom from recovery.
Click to expand...
Click to collapse
Wonder if it got locked while on something it shouldn't have been.
Who relocked it, you or the seller/previous user?
I know in some cases relocking a boot loader on a custom recovery and kernel/ROM basically renders the device useless as it can't boot in either direction if it doesn't have fast boot available.
Perhaps the better course here is to fast boot a stock recovery to it, and maybe a stock boot.img, but it'll maybe take a few tries to find the right version to pass, unless the hboot version is ROM version specific.
Just an idea.
Tapatalked from my HTC DNA - ReVolt
I'm getting ready for a job interview and read this thread too fast, but send me a PM if you would like my help and I will help you get things figured out later today.
I put the badass in Team BAMF
CharliesTheMan said:
I'm getting ready for a job interview and read this thread too fast, but send me a PM if you would like my help and I will help you get things figured out later today.
I put the badass in Team BAMF
Click to expand...
Click to collapse
I am in the SAME boat with this phone.. How did you guys make out? LOCKED bootloader, S-ON.
I had this same problem as well. I was able to get it to boot by flashing the 2.06 firmware found here: http://forum.xda-developers.com/showthread.php?t=2314771
Someone had a custom rom on this DNA, and somehow relocked it with it on. So now, I have a custom rooted rom, but I cannot get the Moonshine (fails on temproot- maybe because its already rooted?) or Revone to work to clean up the mess.
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