I have read on various threads that when you send your phone for service, it typically comes back with latest firmware, and as a result, latest hboot 1.56. Would the device be considered for repair under warrenty if it is completely stock, s-on, latest firmware, but older hboot? This way the device firmware might not be upgraded during service and being on a lower hboot might make it easier to obtain s-off post service. Thoughts?
b99721 said:
I have read on various threads that when you send your phone for service, it typically comes back with latest firmware, and as a result, latest hboot 1.56. Would the device be considered for repair under warrenty if it is completely stock, s-on, latest firmware, but older hboot? This way the device firmware might not be upgraded during service and being on a lower hboot might make it easier to obtain s-off post service. Thoughts?
Click to expand...
Click to collapse
if everything is up to date except the hboot, they will know you have tampered the phone and your warranty will not be valid.
Ok get it. Thanks.
Now can someone please point me to the source for hboot 1.56 (I am on 4.19.1540.9, but had flashed hboot 1.44 and need to revert to original hboot version). I am looking for only hboot and not complete ruu (dont hv bandwidth to download ruu). Quick response would really really help.
Sent from my HTC One using Tapatalk
https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
You need the original unmodified.. these are GSM Only. By the way, does your bootloader say tampered, locked/relocked or does it just say locked.
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
You need the original unmodified.. these are GSM Only. By the way, does your bootloader say tampered, locked/relocked or does it just say locked.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks!
My bootloader says unlocked - I had locked it day before yesterday (at that time it said Locked) but I have unlocked it again now so it says Unlocked. And am s-off. Mine is single sim gsm only phone and firmware is 4.19.1540.9. So which hboot to download? Will hboot for version 4.19.401.9 work on my device and be considered stock for it by service center?
Sent from my HTC One using Tapatalk
That will work ok, But... That's not the answer.. in order to return for warranty.. You phone has to be locked not relocked. Have tampered removed. Stock recovery. In other words out of the box software..
Take a look here
http://forum.xda-developers.com/showthread.php?t=2541082
Do not under any circumstances go S-On yet..
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
That will work ok, But... That's not the answer.. in order to return for warranty.. You phone has to be locked not relocked. Have tampered removed. Stock recovery. In other words out of the box software..
Take a look here
http://forum.xda-developers.com/showthread.php?t=2541082
Do not under any circumstances go S-On yet..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sure I will install stock recovery and do Lock (not relock). Thanks again!
I can unroot after Locked? From the super user app itself?
I plan to follow steps:
1) flash hboot 1.56
2) flash stock recovery
3) get Locked
4) unroot from app
5) factory reset
6) get s-on
Sent from my HTC One using Tapatalk
b99721 said:
Sure I will install stock recovery and do Lock (not relock). Thanks again!
I can unroot after Locked? From the super user app itself?
I plan to follow steps:
1) flash hboot 1.56
2) flash stock recovery
3) get Locked
4) unroot from app
5) factory reset
6) get s-on
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Be careful with hboot 1 56.
If you go S-On. You may not be able to go S-Off again. Also make sure if you go S-On to do so before Ota 3.**.***.*.
Quote" Step 3: if YOU decide to go S-On*(Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55" End Quote. Thank you @nkk71
Though I see no reason to take OTA updates all the way to hboot1.55/1.56.
Not everyone I imagine wants to be on the latest firmware.
Has long as it's fully stock , HTC will honour the Warranty.
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
Be careful with hboot 1 56.
If you go S-On. You may not be able to go S-Off again. Also make sure if you go S-On to do so before Ota 3.**.***.*.
Quote" Step 3: if YOU decide to go S-On*(Note: this should only be done for warranty or selling the phone, it is not needed for OTAs)
fastboot oem writesecureflag 3
reboot 3 times and make sure it doesnt say "tamper detected - rebooting" and then shows TAMPERED again
as far as I know, this was introduced in hboot 1.55" End Quote. Thank you @nkk71
Though I see no reason to take OTA updates all the way to hboot1.55/1.56.
Not everyone I imagine wants to be on the latest firmware.
Has long as it's fully stock , HTC will honour the Warranty.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So you are suggesting I first downgrade and then achieve s-on? I am ok with no s-off. Getting warranty is more important for me at this point. I want to be on the latest firmware. So if I go s-on with hboot 1.56, I will be in a fix? In that case can I s-on with present hboot 1.44 and then flash hboot 1.56? Or it will not be possible since i would be s-on?
Sent from my HTC One using Tapatalk
bored_stupid said:
That will work ok, But... That's not the answer.. in order to return for warranty.. You phone has to be locked not relocked. Have tampered removed. Stock recovery. In other words out of the box software..
Take a look here
http://forum.xda-developers.com/showthread.php?t=2541082
Do not under any circumstances go S-On yet..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The hboot file didn't work. So I extracted it from the OTA file I had with me for 4.19.1540.9 and replaced the hboot img file in the zip I had for hboot 1.44. Worked!
But it was scary - I executed fasboot flash zip command and the progress bar n the phone was stuck around 75% but cmd returned OK. So as per instructions on htc1guru, I executed the command again and the status bar didn't move but again cmd said OK. Finally turned off the phone by holding down power button and prayed and turned it on. Phone booted with hboot 1.56!
PS: Exactly same thing had happened when I had downgraded to hboot 1.44
Sent from my HTC One using Tapatalk
Sorry should have mentioned that. It goes like this..
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip hboot.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. *You have to issue the exact command again:
fastboot flash zip hboot.zip
The green status bar usually does not reach the 100% mark. *When the output in the command window is complete, you can reboot:
fastboot reboot
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
Sorry should have mentioned that. It goes like this..
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip hboot.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. *You have to issue the exact command again:
fastboot flash zip hboot.zip
The green status bar usually does not reach the 100% mark. *When the output in the command window is complete, you can reboot:
fastboot reboot
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the instructions! My phone has left country now! Will save one way courier money and hopefully get in warranty service - sent with s-off, but Locked.
b99721 said:
Thanks for the instructions! My phone has left country now! Will save one way courier money and hopefully get in warranty service - sent with s-off, but Locked.
Click to expand...
Click to collapse
Hope all goes well.
Sent from my HTC One using XDA Premium 4 mobile app
bored_stupid said:
Hope all goes well.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got my One back! Camera is awesome now. Low light, normal light, sunlight... every situation the camera excels.
Sensor is ov6488, no date.
Only thing that that is bugging me, but I can live with it - using flash results in a very light green hue on the entire photograph. But I rarely use flash.
And the camera lens (and the flash module) are a little off-center from glass at the back, but it seems to have no effect on the photos, so I am fine (but just a little annoyed) with it.
At the same time, I want to confirm a couple of things -
1) Does this sensor have OIS - had read somewhere it is same sensor as the one used in M8, which doesn't have OIS
2) The photos appear distorted towards the ends/edges - a characteristic of the wide angle lense I understand - but with the prior sensor, when I use to set Crop as Regular, the photos use to get straight at ends/edges; but that is not the case anymore - no matter what Crop I select - Wide, Regular, and Square, photos are distorted/wide at ends/edges. Hope this is the way it is suppose to be.
Sent from my HTC One using Tapatalk
Related
PLEASE READ: This will only work on a stock, signed S-OFF HBOOT. Do not try this on a patched or ENG HBOOT or the result will be a permanent hard brick.
1. Boot into fastboot on your device
2. Open a terminal or command prompt and navigate to where your fastboot binary is.
3. Type the following commands:
Code:
fastboot devices
Ensure your device is listed
_________________________________
Code:
fastboot oem readsecureflag
The output should read something like: secure_flag: 0
_________________________________
Code:
fastboot oem writesecureflag 3
_________________________________
Last:
Code:
fastboot reboot bootloader
Verify that your device is now S-ON
Thanks to Blue6IX for original tutorial
Thanks for this man, I was wondering when someone would come up with this. People will need it to fully return to stock.
Sent from my HTC PH39100 using xda premium
Thanks bud. Logic would suggest you could enter 0 to give s off inplace of 3 to return to s on.
Sent from my HTC Velocity 4G using XDA Premium App
78cortina said:
Thanks bud. Logic would suggest you could enter 0 to give s off inplace of 3 to return to s on.
Sent from my HTC Velocity 4G using XDA Premium App
Click to expand...
Click to collapse
No that will not work, you will have to run the S-Off tool again to regain it.
Awesome thank you
Sent from my HTC PH39100 using XDA
hey cruzin long time, how u been?
do you know if this will return you to a "LOCKED" stated instead of RELOCKED?
lebmb said:
hey cruzin long time, how u been?
do you know if this will return you to a "LOCKED" stated instead of RELOCKED?
Click to expand...
Click to collapse
I tried it... can confirm that u first what I did was lock bootlader run stock rom like ruu and then do these steps.... It will say locked and s on
Sent from my HTC PH39100 using XDA
Marshmellow92 said:
I tried it... can confirm that u first what I did was lock bootlader run stock rom like ruu and then do these steps.... It will say locked and s on
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
that's what i thought
thanks
Just clarifying something, so this will or will NOT work for the ics hboot posted on the s-off site by juopunutbear?
slapshot30 said:
Just clarifying something, so this will or will NOT work for the ics hboot posted on the s-off site by juopunutbear?
Click to expand...
Click to collapse
It will, just as long as you chose the non-patched hboot without fastboot commands.
Just had to use this method.
Used the PH39IMG to get back to a stock hboot and ran the commands. Confirmed that it does display locked in hboot.
Unlocked, reflashed recovery.. and I am good to go s-on
Sent from my HTC PH39100 using XDA
Where can I find the steps on flashing the PH39IMG to get back stock hboot ?
dynamiclynk said:
Where can I find the steps on flashing the PH39IMG to get back stock hboot ?
Click to expand...
Click to collapse
Superuser guide opt 6
http://forum.xda-developers.com/showthread.php?t=1416836
Just FYI it reboots once during the process let it do it's thing don't interrupt it.
esloan said:
Superuser guide opt 6
http://forum.xda-developers.com/showthread.php?t=1416836
Just FYI it reboots once during the process let it do it's thing don't interrupt it.
Click to expand...
Click to collapse
Thanks!
Yeah seems the
SECOND OPTION (PH39IMG.zip flash) <-- link dead
So can I do OPTION ONE and download the correct RUU and do the same or does the PH39IMG.zip have something the RUU does not ?
dynamiclynk said:
Thanks!
Yeah seems the
SECOND OPTION (PH39IMG.zip flash) <-- link dead
So can I do OPTION ONE and download the correct RUU and do the same or does the PH39IMG.zip have something the RUU does not ?
Click to expand...
Click to collapse
The RUU will do the trick.
Sent from my HTC Holiday using xda premium
Curious. Could you write the secureflag to 0?
Sent from my HTC PH39100 using XDA
mibikin said:
Curious. Could you write the secureflag to 0?
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Nope ,
Sent from my HTC PH39100 using XDA
after i say
fastboot oem readsecureflag
The output is : secure_flag: 3
can i proceed to safety or killing the phone?
i did a s off through HTC by the way
Marshmellow92 said:
I tried it... can confirm that u first what I did was lock bootlader run stock rom like ruu and then do these steps.... It will say locked and s on
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
So for all intents and purposes, it will look like it was never HTC Unlocked then? My g/f has a Vivid, and she's very picky about going to the darkside of rooting, because she doesn't want her warranty voided. If it can look like it's been returned to stock, that would help.
I cant get it to say ***LOCKED*** I locked hboot, ran GB RUU, ran ICS RUU, followed your steps, fastboot oem readsecureflag
Output is : secure_flag: 3
***RELOCKED***
S-ON
Did I do something wrong?
Hello there!!!.....Really need some help form you HTC experts. Here is my problem, my htc is currently stuck at the screen where all i am seeing is the htc logo with four exclamation marks in the 4 corners. 1. whenever i tried to run the RUU (run as administrator) i would get a error 152, and this is with my bootloader locked. now i read through a few forums and this one guy told me to change back to S on, now that i have done so when ever i try to run the ruu i get error 132. can anyone please assist?
Do you have a custom recovery on your device? And a backup? If so hold your phone up to a light and hold power and volume down it should boot into fast boot from there boot into recovery and restore your back up
Sent from my SGH-T989D using xda app-developers app
offwiththeface said:
Do you have a custom recovery on your device? And a backup? If so hold your phone up to a light and hold power and volume down it should boot into fast boot from there boot into recovery and restore your back up
Sent from my SGH-T989D using xda app-developers app
Click to expand...
Click to collapse
no custom rom installed.....no backup either.
Are you still on hboot 1.44?
If yes, s-off again.
If no, going s-on was probably a terrible mistake.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
Are you still on hboot 1.44?
If yes, s-off again.
If no, going s-on was probably a terrible mistake.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes i am still on hboot 1.44. how do i s off with the device stuck in ruu?
altezza1 said:
yes i am still on hboot 1.44. how do i s off with the device stuck in ruu?
Click to expand...
Click to collapse
Definitely get back s-off !!! It will have zero effect (now or in the future) about locked/unlocked, custom/stock rom, OTAs, etc. but it would allow you to flash unsigned firmware and/or downgrade, which is very important if you want to run a RUU.
If you flash a custom recovery, you can issue the revone ADB commands in the recovery screen.
EDIT: once you have s-off, you need to change your CID to SuperCID to run the RUU
just make sure you're using a Sprint version RUU or custom ROM, as Sprint is different from ATT, international, etc.
nkk71 said:
Definitely get back s-off !!! It will have zero effect (now or in the future) about locked/unlocked, custom/stock rom, OTAs, etc. but it would allow you to flash unsigned firmware and/or downgrade, which is very important if you want to run a RUU.
If you flash a custom recovery, you can issue the revone ADB commands in the recovery screen.
EDIT: once you have s-off, you need to change your CID to SuperCID to run the RUU
just make sure you're using a Sprint version RUU or custom ROM, as Sprint is different from ATT, international, etc.
Click to expand...
Click to collapse
The only problem with that plan is that i am stuck in RUU boot, and i can only do fastboot commands. how do that?
altezza1 said:
The only problem with that plan is that i am stuck in RUU boot, and i can only do fastboot commands. how do that?
Click to expand...
Click to collapse
You can/have to flash recovery using fastboot anyway.
I believe it's "fastboot flash recovery <filename>"
Sent from my HTC One using xda app-developers app
I have an HTC one running 4.3 google play I want it to be back to stock so I can sell it. It was originially running Bell mobility but I could not find an RUU for Bell but I found some OTA's for bell. how would I go about this, is it possible? Can I use another RUU and then flash the OTA for bell would that work?
If anyone has a bell RUU that would help alot thank you.
(Canada)
If you fully converted to GPe, then you have s-off. Change the CID and flash a WWE Developers Edition RUU.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
If you fully converted to GPe, then you have s-off. Change the CID and flash a WWE Developers Edition RUU.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't have s-off I checked in the recovery mode it says m7_UL PVT SHIP S-ON RW.
How do I change CID?
iBillz said:
I don't have s-off I checked in the recovery mode it says m7_UL PVT SHIP S-ON RW.
How do I change CID?
Click to expand...
Click to collapse
You can't with s-on. Flash a backup of your carriers stock rom and a stock recovery. Your phone will still say Tampered and Relocked.
Sent from my HTC One using XDA Premium 4 mobile app
CoryTallman said:
You can't with s-on. Flash a backup of your carriers stock rom and a stock recovery. Your phone will still say Tampered and Relocked.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The goal is for it to go back to a stock HTC one what should I do from here?
iBillz said:
The goal is for it to go back to a stock HTC one what should I do from here?
Click to expand...
Click to collapse
If you never S-off before then you haven't changed your CID. If that's the case then follow @Mike1986 guide to going back to stock. Use method 3.: http://forum.xda-developers.com/showthread.php?t=2265618. Grab the CWM stock Nandroid for your device from here: http://forum.xda-developers.com/showpost.php?p=45187010&postcount=1. [deleted]
That should work as long as you haven't changed your CID before.
Correction: That nandroid should have the stock recovery in it, if it's not then you'll have to search for it and flash it via fastboot. My apologies.
farang4u said:
If you never S-off before then you haven't changed your CID. If that's the case then follow @Mike1986 guide to going back to stock. Use method 3.: http://forum.xda-developers.com/showthread.php?t=2265618. Grab the CWM stock Nandroid for your device from here: http://forum.xda-developers.com/showpost.php?p=45187010&postcount=1. It has the stock recovery in it.
That should work as long as you haven't changed your CID before.
Click to expand...
Click to collapse
Will following what you said make the root untraceable. Meaning the warranty will be unvoided?
iBillz said:
Will following what you said make the root untraceable. Meaning the warranty will be unvoided?
Click to expand...
Click to collapse
No, because your bootloader will indicate "Re-locked" instead of "Locked". Also, your IMEI was registered in HTC's database when you unlocked the bootloader via htcdev website. Only way to cover some of your tracks is to S-off the device by Revone if possible and using their lock command. It involves some risk. Rooting the phone doesn't always void the warranty, many times they'll will honor it if it's a genuine hardware issue.
.
flashing bell firmware help
hi, i wanted to know if there is any way of fixing a touchscreen problem after flashing a firmware, the system is all fine, i have s-on, bootloader locked and also stock recovery with stock rom, but the touchscreen does not work, wondering if i could get some help ( firmware 1.29.666.17 bell canada). thank you.
farang4u said:
No, because your bootloader will indicate "Re-locked" instead of "Locked". Also, your IMEI was registered in HTC's database when you unlocked the bootloader via htcdev website. Only way to cover some of your tracks is to S-off the device by Revone if possible and using their lock command. It involves some risk. Rooting the phone doesn't always void the warranty, many times they'll will honor it if it's a genuine hardware issue.
Click to expand...
Click to collapse
When I try and flash the Nandroid backup it says failed? am I missing something? I ran a factory reset before hand
iBillz said:
When I try and flash the Nandroid backup it says failed? am I missing something? I ran a factory reset before hand
Click to expand...
Click to collapse
You don't flash a nandroid. You unzip it and use the restore function.
Sent from my HTC One using XDA Premium 4 mobile app
My HTC One is actually an AT&T version and I successfully turned it into a Google Play edition with 4.4 Kit Kat. I now need to turn it back into the AT&T version but everything is failing and I relocked the bootloader and it will not unlock again even though the Unlock_code.bin says it was successful when ran. It never goes to the unlock bootloader splash screen on the phone to actually unlock it. Somehow it's a mess. I still have s-off. Is there a bootloader unlock via s-off? I'd like to flash the AT&T stock recovery and relock it and flash the AT&T 4.3 rom if possible. Any help would be appreciated, thank you!
http://forum.xda-developers.com/showthread.php?t=2475914
This should be in the Q and A forum as well
Sent from my HTC One using XDA Premium 4 mobile app
gusto5 said:
http://forum.xda-developers.com/showthread.php?t=2475914
This should be in the Q and A forum as well
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This procedure requires the phone to be rooted.
is there anyway to either:
a) Root the phone with a locked bootloader if you have s-off?
or
b) unlock the bootloader without using S-off without using HTCDev?
basically I dont want to loose all my settings and date and re-install everything.
kiwiandy said:
This procedure requires the phone to be rooted.
is there anyway to either:
a) Root the phone with a locked bootloader if you have s-off?
or
b) unlock the bootloader without using S-off without using HTCDev?
basically I dont want to loose all my settings and date and re-install everything.
Click to expand...
Click to collapse
I don't know about not losing anything but I did manage to get mine back to being at&t again thankfully. You definitely have to change the cid and I used the decrypted stock at&t rom from the htc1guru website. I'm pretty sure it's the same as the ruu.exe downloaded directly from HTC. My phone flushed the hboot and then flushed the rest of it in ruu mode. I still have s-off and I'm leaving my bootloader locked. I bet it will unlock now though.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
galaxyjeff said:
I don't know about not losing anything but I did manage to get mine back to being at&t again thankfully. You definitely have to change the cid and I used the decrypted stock at&t rom from the htc1guru website. I'm pretty sure it's the same as the ruu.exe downloaded directly from HTC. My phone flushed the hboot and then flushed the rest of it in ruu mode. I still have s-off and I'm leaving my bootloader locked. I bet it will unlock now though.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
you can use this to easily lock/unlock at any time using custom recovery: http://forum.xda-developers.com/showthread.php?t=2527194 (for TWRP need 2.6.3.3 or higher)
nkk71 said:
you can use this to easily lock/unlock at any time using custom recovery: http://forum.xda-developers.com/showthread.php?t=2527194 (for TWRP need 2.6.3.3 or higher)
Click to expand...
Click to collapse
Thank you. I think it will go back to unlocking now that I'm back on an att rom. I don't like that Google edition 4.4 rom. It takes away beats audio even though it says it still has it.
Sent from my HTC One using Tapatalk
I have one of the bad camera sensors, and rather than live with it I'm hoping HTC can fix it.
I unlocked the bootloader on my device, and I was wondering: would HTC refuse service for this? Also, should I go S-Off and remove the "tampered with" message?
Any advice would be appreciated!
Definitely relock and remove tampered label using revone
Sent from my HTC One using xda premium
Stock ROM, CWM Recovery
SmallMan123 said:
Definitely relock and remove tampered label using revone
Sent from my HTC One using xda premium
Stock ROM, CWM Recovery
Click to expand...
Click to collapse
Well crap. Thanks for the prompt response!
I assume that also means I should revert to the stock ROM. Or would the Google Play ROM be be OK?
michaelalias said:
Well crap. Thanks for the prompt response!
I assume that also means I should revert to the stock ROM. Or would the Google Play ROM be be OK?
Click to expand...
Click to collapse
ReLOCKED isn't really recommended
S-off is usually okay, but RELOCKED, hmmm.
Might wanna look at my guide.
Sent from my HTC One using Tapatalk
Now I'm not sure what to do. I'm working on S-Off right now to remove the tampered. Aside from flashing a stock ROM (I'll assume for now Google Play edition is fine), is there anything else I should do?
michaelalias said:
Now I'm not sure what to do. I'm working on S-Off right now to remove the tampered. Aside from flashing a stock ROM (I'll assume for now Google Play edition is fine), is there anything else I should do?
Click to expand...
Click to collapse
Honestly, you should go completely stock (with the software that came with your phone, i.e dont leave it gpe if it was sense based etc). Look @nkk71's guide to going stock, all the info you need is there
You can leave it s-off if you please but i would definitely LOCK the bootloader instead of RELOCKING since ive heard/read a few cases where they didn't fix the device since it was re-locked making it void of its warranty. Now personally, i would even go as far as S-ON, just to be on the safe side. I can attest that ive s-offed with rumrunner, s-oned, and then s-offed again with rumrunner (on my device) and it worked so you can s-off again when you get the device back.
Then once you get the device back you don't have to start all the way from the beginning with htc-dev, just use the same unlock code you got the first time(if you don't have it saved you can check the email it was sent in), and then proceed from the last step that was flash it in adb to unlock your phone again
Yeah sorry I meant relock as in lock bootlosder so on top it says *LOCKED*
Sent from my HTC One using xda premium
Stock ROM, CWM Recovery