Alright, I'm having issues with my phone. I've been a huge procrastinator about this, and I need to set it all back to factory settings. Factory recovery, and locked. How can I do this real quick?
I'm running on the Stock ROM at the moment, with S-ON. Need any more information let me know! All help is appreciated
Flash the RUU. But the only way you will get the bootloader to say "Locked" is if you S-Off then flash the RUU. Otherwise you can only retain a "ReLocked" status.
Double0EK said:
Flash the RUU. But the only way you will get the bootloader to say "Locked" is if you S-Off then flash the RUU. Otherwise you can only retain a "ReLocked" status.
Click to expand...
Click to collapse
I'm returning it for a hardware issue, so that shouldn't matter. I just need to get rid of the custom recovery and what not. Can you point me to the right RUU? I have t-mobile. If you need to know that.
Found: http://d-h.st/users/krook6023/?fld_id=1506#files
I'm not sure WHAT one I use. Obviously none of the ICS as I'm on GB.. but, I need to flash one of these to set it back to factory so I can send it into T-Mobile, hardware issue. I'm sure they'll just wipe the device clean once they get it, but wouldn't mind sending it in after I cleaned it.
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
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
I have a HTC Droid DNA, S-Off with the Eng HBoot, unlocked and rooted. I have a need to get back to at minimum re-locked and stock ROM. (Not sure if it's possible to be S-Off and the rest stock, so forgive me if I am stating something "noobish.")
Can anyone please help me accomplish this? Directions don't have to be 100% detailed, but at least the steps to do so should be accurate. Example response:
Flash stock HBoot (link to process if available)
Re-lock phone
Flash RUU (with link to files)
Really appreciate any and all assistance with this. I have to get the phone unrooted and re-locked minimally as I changed my HBoot to display "Locked, S-On" with stock version info, so I don't think that anyone will be able to tell it's actually not. (In fact, that may be the best bet that way it doesn't say "relocked" etc.)
WorldOfJohnboy said:
I have a HTC Droid DNA, S-Off with the Eng HBoot, unlocked and rooted. I have a need to get back to at minimum re-locked and stock ROM. (Not sure if it's possible to be S-Off and the rest stock, so forgive me if I am stating something "noobish.")
Can anyone please help me accomplish this? Directions don't have to be 100% detailed, but at least the steps to do so should be accurate. Example response:
Flash stock HBoot (link to process if available)
Re-lock phone
Flash RUU (with link to files)
Really appreciate any and all assistance with this. I have to get the phone unrooted and re-locked minimally as I changed my HBoot to display "Locked, S-On" with stock version info, so I don't think that anyone will be able to tell it's actually not. (In fact, that may be the best bet that way it doesn't say "relocked" etc.)
Click to expand...
Click to collapse
The way to go back to relocked and stock is to run the command "fastboot oem lock" and lock the bootloader, and then simply run the 1.15 RUU which is an exe that you run from the computer, it's really easy. That will replace the hboot too though with the stock hboot and will display stock hboot, and relocked. It wont say tampered though because it also installs the stock recovery when you run the RUU
That process is quite easy, I guess if you really wanted to get rid of the relocked sign you could then unlock the bootloader, and flash a custom one. Then it will be stock rom and recovery and kernel no root access from the system and then would display that it was locked and s on when in reality it would be unlocked and s off.
No idea about how to be locked and have a custom hboot, that's above my paygrade. Not saying you can't do it easily but I don't advise on subjects I'm clueless about.
CharliesTheMan said:
No idea about how to be locked and have a custom hboot, that's above my paygrade. Not saying you can't do it easily but I don't advise on subjects I'm clueless about.
Click to expand...
Click to collapse
Firstly, thank you...
Secondly, LOL on the paygrade.
I forgot to mention that I changed the Splash screen... I am assuming flashing the RUU will also overwrite that as well? (I would assume, especially if the HBoot gets flashed.)
WorldOfJohnboy said:
Firstly, thank you...
Secondly, LOL on the paygrade.
I forgot to mention that I changed the Splash screen... I am assuming flashing the RUU will also overwrite that as well? (I would assume, especially if the HBoot gets flashed.)
Click to expand...
Click to collapse
Just flash a stock splash screen before you ruu incase it doesn't overwrite it
Sent from my HTC6435LVW using xda app-developers app
Is there any way for me to return to stock-unrooted with a reloacked bootloader after updating to the latest ota?
I need to relock my phone and return it to stock to send back for a replacement under extended warranty.
I don't think I can't run any of the older ruu files because I am on the current hboot, right?
What is the best way to get this phone back to stock conditions with a relocked bootloader?
I'm s on btw running ecliptic rez now
Sent from my ADR6425LVW using xda app-developers app
So you don't happen to have a nandroid of stock from before flashing a custom ROM?
If not, as seems to be the case since you're posting here, here's a stock ROM based on the OTA that would probably be your best bet:
http://forum.xda-developers.com/showthread.php?t=2260154&highlight=stock+ota
ETA: I don't know if the link on the first page got changed but here's a fixed link for proper MD5 matching on the second page:
http://forum.xda-developers.com/showthread.php?t=2260154&highlight=stock+ota&page=2
feralicious said:
So you don't happen to have a nandroid of stock from before flashing a custom ROM?
If not, as seems to be the case since you're posting here, here's a stock ROM based on the OTA that would probably be your best bet:
http://forum.xda-developers.com/showthread.php?t=2260154&highlight=stock+ota
ETA: I don't know if the link on the first page got changed but here's a fixed link for proper MD5 matching on the second page:
http://forum.xda-developers.com/showthread.php?t=2260154&highlight=stock+ota&page=2
Click to expand...
Click to collapse
If I load that rom onto my rezound I'm attempting to restore to stock to return, is there a way to unroot it and return it fully to stock from there?
ryryrocco said:
Is there any way for me to return to stock-unrooted with a reloacked bootloader after updating to the latest ota?
I need to relock my phone and return it to stock to send back for a replacement under extended warranty.
I don't think I can't run any of the older ruu files because I am on the current hboot, right?
What is the best way to get this phone back to stock conditions with a relocked bootloader?
Click to expand...
Click to collapse
I discovered 2 options. Wait till an RUU is released for .14, or go S-OFF, RUU to .2, then reset the S flag to on.
(1) Stock-Rooted 4.05.605.14 rom, loadable from recovery (post #3)... probably not necessary if you can boot now, but probably the most likely to work since its completely stock other than root: http://forum.xda-developers.com/showthread.php?t=2288479
(2) Windows S-Off files (post 361): http://forum.xda-developers.com/showthread.php?p=40950251#post40950251
(3) Follow these directions to S-OFF: http://unlimited.io/juopunutbear.htm
*** The timing of the wire trick is tricky, took me a good 6 or 7 tries to get it right.
(4) I had to follow the section under ROM Recovery to get it booting again after S-OFF: http://unlimited.io/jbtroubleshooting.htm
(5) Followed this guide to reset my locked flag (since I unlocked after going S-Off /facepalm... if you don't unlock after S-Off, you shouldn't need to do this part): http://androidforums.com/rezound-all-things-root/659453-how-reset-your-lock-status-flag.html
(6) Last but not least, follow this guide to go back to S-ON (You MUST run the RUU before doing this last step or you risk bricking your device!): http://androidforums.com/rezound-al...-off-guide-info-return-stock.html#post4394129
Make sure you read each step carefully... it worked for me... YMMV.
Result: Fully stock, locked, and S-ON, to send back to VZW
flamewalker said:
If I load that rom onto my rezound I'm attempting to restore to stock to return, is there a way to unroot it and return it fully to stock from there?
Click to expand...
Click to collapse
You can probably flash a stock recovery and relock it. Without s-off your phone will always say "Relocked" in the bootloader. A lot of people have returned their phones that way and said they didn't have a problem, but if you do, don't hold me to that, but there are posts you can find saying this.
Or you can go the more involved route that was posted just above.
Oh, thought I was responding to original poster... anyway, info still valid.
feralicious said:
You can probably flash a stock recovery and relock it. Without s-off your phone will always say "Relocked" in the bootloader. A lot of people have returned their phones that way and said they didn't have a problem, but if you do, don't hold me to that, but there are posts you can find saying this.
Or you can go the more involved route that was posted just above.
Oh, thought I was responding to original poster... anyway, info still valid.
Click to expand...
Click to collapse
Yeah... I spent a good 2 to 3 hours figuring that out Finished the final S-ON and restore process about 1am last night.
I wanted to eliminate any possible chance of them trying to claim it was because I borked the software by messing with it... I knew it was a slim chance, but I just didn't want to risk it. The risk of going S-OFF outweighed the risk of VZW blaming me for the failed touch screen. Each person needs to decide whether the risks are worth it to them
And, doing the S-OFF stuff was actually kind of fun! (I love to tinker!)
Hey guys, a little help over here!
My M8 At&t variant is unlocked, have a tampered banner but is S-On and I don't know which recovery I'm using. When I go in recovery it gets stuck showing a red triangle. I want to go fully stock and unroot to get lollipop update. Will running RUU solve it?
77tammy7 said:
I don't know which recovery I'm using.
Click to expand...
Click to collapse
Why not? This statement implies that you are either messing with the phone without proper knowledge; or doing so in a manner that is careless, and not keeping track of what you are flashing to the phone. Either way, its worrisome.
77tammy7 said:
When I go in recovery it gets stuck showing a red triangle. I want to go fully stock and unroot to get lollipop update. Will running RUU solve it?
Click to expand...
Click to collapse
Red triangle is stock recovery.
The RUU will certainly restore you to full stock. And you can RUU right up to Lollipop, without having to take an update to do so.
Since you are s-on, you need to relock the bootloader to run the RUU.
Keep in mind that the RUU will wipe user data, so backup anything you want to keep (preferebly backup to an off-phone location) before you RUU.
redpoint73 said:
Why not? This statement implies that you are either messing with the phone without proper knowledge; or doing so in a manner that is careless, and not keeping track of what you are flashing to the phone. Either way, its worrisome.
Red triangle is stock recovery.
The RUU will certainly restore you to full stock. And you can RUU right up to Lollipop, without having to take an update to do so.
Since you are s-on, you need to relock the bootloader to run the RUU.
Keep in mind that the RUU will wipe user data, so backup anything you want to keep (preferebly backup to an off-phone location) before you RUU.
Click to expand...
Click to collapse
Actually I got that phone from a friend, in used form, that's why I didn't know about recovery. Anyways, will I have to unroot and remove the tampered banner to RUU or just relock the bootloader?
Thanks.
77tammy7 said:
will I have to unroot and remove the tampered banner to RUU or just relock the bootloader?
.
Click to expand...
Click to collapse
Just relock the bootloader (fastboot command: fastboot oem lock).
If updating to Lollipop is what you want, the correct RUU is linked at the bottom of the following webpage, along with additional instructions on how to run the RUU (under "Manual system Update instructions"): http://www.htc.com/us/support/htc-one-m8-att/news/
redpoint73 said:
Just relock the bootloader (fastboot command: fastboot oem lock).
Click to expand...
Click to collapse
Thanks alot man. Appreciate it.
77tammy7 said:
Thanks alot man. Appreciate it.
Click to expand...
Click to collapse
There's a button for that.
You're very welcome.