Database Develop

[SOLVED] Can't flash RUU's?

Sorry for creating a lot of help threads, but things just don't wanna work my way.
Yesterday I wanted to flash a RUU to see exactly how HTC does things and if it's easy or hard. Anyway. I come from a Galaxy S3 and if I wanted to go back to stock from any other rom, I simply flashed a stock rom tar with a program called Odin, but it doesn't seem to be as simple with HTC.
I downloaded a RUU for the Europe region as it seemed the most obvious thing to do, but my CID is Nordic (HTC__Y13). Here's how it went:
Being on a 4.2.2 custom rom:
I tried running the RUU when I was on a 4.2.2. custom rom (InsertCoin 2.0.2), and I fired up the RUU file and followed the instructions. Then it said my phone isn't supported and that I need another RUU file.
Being on a stock odexed 1.29 rom:
I then installed a stock 1.29 rom from Mike1986. and then fired up the RUU. I followed the instructions and it seems the flashing started. It sent me to the RUU mode (the HTC screen) and began the flashing process. It said it wiped the data and that it sent some signature keys, I think. Three minutes later, the RUU window disappeared. I could see the program was still running but the window disappeared. It quickly flashed for about half a second and I could see some text saying that my phone isn't supported, but why the hell did it commence the flashing?
I pulled the cable, long-pressed the power button and let it boot, it hadn't wiped a thing.
Let it be known that before I opened the RUU's, I made sure I was bootloader locked and S-ON (with the revone method).
Is it because I have the Nordic CID and I had a RUU for the European region? If so, I looked anywhere and everywhere for a Nordic RUU but there's none to be found.
Any help is appreciated.

You can only use an RUU which is the same or newer than the firmware on the phone, e.g. if your last official update was 1.29.401.13 you could only use an RUU that version or above UNLESS you're S-OFF, in which case you can use an older one if you have Super CID and a locked/relocked bootloader

EddyOS said:
You can only use an RUU which is the same or newer than the firmware on the phone, e.g. if your last official update was 1.29.401.13 you could only use an RUU that version or above UNLESS you're S-OFF, in which case you can use an older one if you have Super CID and a locked/relocked bootloader
Click to expand...
Click to collapse
So what you're saying, is:
If I acquire Super CID, then flash a Europe RUU and then set my CID back to what it originally was (or maybe even set it to HTC__001) and then reflash the RUU, and it'll work beautifully? I'm S-OFF, btw.

Theshawty said:
So what you're saying, is:
If I acquire Super CID, then flash a Europe RUU and then set my CID back to what it originally was (or maybe even set it to HTC__001) and then reflash the RUU, and it'll work beautifully? I'm S-OFF, btw.
Click to expand...
Click to collapse
Where you S-Off or S-On when you ran the RUU?

bobsie41 said:
Where you S-Off or S-On when you ran the RUU?
Click to expand...
Click to collapse
S-ON with the bootloader locked. I wanted to see if it was possible.
I'm not really looking to revert to unrooted stock, at least not now. I just want to know that it's possible without too much work for when it would be necessary or when I want to try out unrooted stock again. It's always nice to have a fallback.

Theshawty said:
S-ON with the bootloader locked. I wanted to see if it was possible.
I'm not really looking to revert to unrooted stock, at least not now. I just want to know that it's possible without too much work for when it would be necessary or when I want to try out unrooted stock again. It's always nice to have a fallback.
Click to expand...
Click to collapse
As far as I'm aware, you can only run a RUU that is relevant to you device whilst you are s-on and only one that is equal to or above the firmware that you are running.
The only way to return to official un-rooted stock is, again, to run a RUU for your device or install a completely stock nandroid backup of your device or one running the same version as yours.

OK, full example...
You originally get an unbranded One from the EU and you get the OTA to 1.29.401.13. From this point on, with an S-ON/Locked phone with CID HTC__001 you can ONLY flash an RUU which is 1.29.401.13 or higher. This will never change. If you get an RUU from a specific carrier you cannot flash it as it doesn't match your CID.
If you unlock the bootloader, but stay S-ON, you cannot flash an RUU at all - you HAVE to relock the bootloader first but you can still only flash an RUU matching your CID and is the same or newer than your current version.
If you S-OFF and change the CID to 11111111 you can flash ANY RUU you want, even those older than your current version, e.g. 1.28.401.7. You still have to have a locked/relocked bootloader but you can stay S-OFF and flash the RUU. As the only RUU available at the moment for the unbranded One is 1.28.401.7 it means you can flash that and then get the OTA updates in sequence to get to the latest version
Once back at the older version using the RUU you could change your CID back to HTC__001 if you wanted but I don't think it matters

EddyOS said:
OK, full example...
You originally get an unbranded One from the EU and you get the OTA to 1.29.401.13. From this point on, with an S-ON/Locked phone with CID HTC__001 you can ONLY flash an RUU which is 1.29.401.13 or higher. This will never change. If you get an RUU from a specific carrier you cannot flash it as it doesn't match your CID.
If you unlock the bootloader, but stay S-ON, you cannot flash an RUU at all - you HAVE to relock the bootloader first but you can still only flash an RUU matching your CID and is the same or newer than your current version.
If you S-OFF and change the CID to 11111111 you can flash ANY RUU you want, even those older than your current version, e.g. 1.28.401.7. You still have to have a locked/relocked bootloader but you can stay S-OFF and flash the RUU. As the only RUU available at the moment for the unbranded One is 1.28.401.7 it means you can flash that and then get the OTA updates in sequence to get to the latest version
Once back at the older version using the RUU you could change your CID back to HTC__001 if you wanted but I don't think it matters
Click to expand...
Click to collapse
Ah, thanks for the clarification! If I do this (Super CID plus flash the RUU), should I change back to the HTC__Y13 cid or change to something like HTC__001 to get the updates for the Europe region? I heard Europe gets OTA's faster than other regions.
One more thing, why does the bootloader have to be locked? Does the RUU check for this?

Theshawty said:
Ah, thanks for the clarification! If I do this (Super CID plus flash the RUU), should I change back to the HTC__Y13 cid or change to something like HTC__001 to get the updates for the Europe region? I heard Europe gets OTA's faster than other regions.
One more thing, why does the bootloader have to be locked? Does the RUU check for this?
Click to expand...
Click to collapse
If you wish to get ota's you will need to have a cid which is relevant to the RUU you have run. Either of those cid's should work for a x.xx.401.x RUU. Not sure about the bootloader locking for an RUU.

bobsie41 said:
If you wish to get ota's you will need to have a cid which is relevant to the RUU you have run. Either of those cid's should work for a x.xx.401.x RUU. Not sure about the bootloader locking for an RUU.
Click to expand...
Click to collapse
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.

Theshawty said:
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Click to expand...
Click to collapse
Not necessarily. As with the s3, releases seem pretty random from country to country in Europe. I had the one x with HTC__001 cid and was one of the last to be updated.
Sent from my Nexus 7 using xda premium

Locked the bootloader and went into fastboot and started the RUU. It is now flashing :victory:
After it's done, I will turn the CID back to HTC__Y13 and reflash the RUU.

Theshawty said:
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Click to expand...
Click to collapse
I, personally, would relock the bootloader purely to cover yourself. As for CID, it's up to you. Using HTC__001 might not get it the second an OTA comes out but I'm sure you're patient enough to wait a few days

EddyOS said:
I, personally, would relock the bootloader purely to cover yourself. As for CID, it's up to you. Using HTC__001 might not get it the second an OTA comes out but I'm sure you're patient enough to wait a few days
Click to expand...
Click to collapse
I just want back to stock for a few days. I'm a bit tired of custom roming yet I can't stay away from it!

Theshawty said:
I just want back to stock for a few days. I'm a bit tired of custom roming yet I can't stay away from it!
Click to expand...
Click to collapse
I've done the same with my Nexus 4, and shall do the same with my One when I get it next month. I want S-OFF purely because the only RUU we have is an older than what I'll likely get on my phone. This way I can always go back to stock (unless a newer RUU leaks that is!)

How awfully peculiar, though. After I flashed to stock (the 1.28 something RUU), I got an update to 1.29.401.12. My brother, whom also have a One in the same region as I, has the 1.29.401.16 update (I am four decimals behind him ).
I thought I would get an update to .16, or am I just being too impatient?
I know I had .16 before custom roms though.

I read all, very useful conversation,saved me lot of time
Only a thing i havent understand
Im now S-OFF,unlocked with superCID ( runnind a branded italian rom with (now old)TIM__041(if i rememeber right)cid)
What i need to do to have a stock unbranded european RUU
Do i need to relock bootloader Before flashing or not matters?

Theshawty said:
How awfully peculiar, though. After I flashed to stock (the 1.28 something RUU), I got an update to 1.29.401.12. My brother, whom also have a One in the same region as I, has the 1.29.401.16 update (I am four decimals behind him ).
I thought I would get an update to .16, or am I just being too impatient?
I know I had .16 before custom roms though.
Click to expand...
Click to collapse
.16 was for the M7_U handsets, M7_UL is on .12

EddyOS said:
.16 was for the M7_U handsets, M7_UL is on .12
Click to expand...
Click to collapse
But my little brother and I both have UL devices, and his clearly says UL in the about screens.

Theshawty said:
But my little brother and I both have UL devices, and his clearly says UL in the about screens.
Click to expand...
Click to collapse
Hmmm, perhaps it is down to CID then...I don't know anyone in the UK with anything over .12

S-Off Definitive answer needed.

My device is natively 1.28.61.7 cid ORANG001 (UK EE/Orange/T-Mobile) although my bootloader is unlocked and I have been running custom software since I got it.
I have successfully s-offed my device with revone, removed the tampered warning and set super cid just with the fastboot method.
My question is...Can I permanently 'debrand' my device and continually receive and install stock updates by
1 Changing my cid to HTC__001 by the fastboot method.
2 Running a 1.2x.401.x RUU
3 Receive and install ota updates.
Will this scenario work as I have seen many conflicting answers on this forum and, if yes, do I need my bootloader locked or unlocked??
Also, if this scenario proves to be successful, where would it leave me if a subsequent ota update closes the s-off loophole??
Any informed assistance would me much appreciated.

To completely debrand:
S-OFF
Supercid
Flash a unbranded RUU
change your cid to HTC_001( or one you want)
You will receive OTA and all you need

erto90 said:
To completely debrand:
S-OFF
Supercid
Flash a unbranded RUU
change your cid to HTC_001( or one you want)
You will receive OTA and all you need
Click to expand...
Click to collapse
Thanks for your quick answer!
Have you tried this?
Bootloader locked or unlocked?

bobsie41 said:
Thanks for your quick answer!
Have you tried this?
Bootloader locked or unlocked?
Click to expand...
Click to collapse
Bootloader has to be locked or relocked

bobsie41 said:
Thanks for your quick answer!
Have you tried this?
Bootloader locked or unlocked?
Click to expand...
Click to collapse
yup tried with my friend's phone, unlocked bootloader before and after :good:

erto90 said:
yup tried with my friend's phone, unlocked bootloader before and after :good:
Click to expand...
Click to collapse
......so I change cid to HTC__001 , lock bootloader run RUU 1.2x.401.xx then update, update..for evermore stock unbranded????
Would just like to be certain

bobsie41 said:
......so I change cid to HTC__001 , lock bootloader run RUU 1.2x.401.xx then update, update..for evermore stock unbranded????
Would just like to be certain
Click to expand...
Click to collapse
you DO NOT need to lock bootloader
it can stay unlocked
and you NEED supercid to flash the RUU
after flashed RUU, change you cid to HTC_001

erto90 said:
you DO NOT need to lock bootloader
it can stay unlocked
and you NEED supercid to flash the RUU
after flashed RUU, change you cid to HTC_001
Click to expand...
Click to collapse
Even to apply ota?

bobsie41 said:
Even to apply ota?
Click to expand...
Click to collapse
to apply ota you can be locked or unlocked.. is the same

erto90 said:
you DO NOT need to lock bootloader
it can stay unlocked
and you NEED supercid to flash the RUU
after flashed RUU, change you cid to HTC_001
Click to expand...
Click to collapse
It's HTC__001, not HTC_001 - the double underscore is essential

EddyOS said:
It's HTC__001, not HTC_001 - the double underscore is essential
Click to expand...
Click to collapse
is changing the CID purely for official OTA's?
I really dont get it if youre running a ROM. heh

EddyOS said:
It's HTC__001, not HTC_001 - the double underscore is essential
Click to expand...
Click to collapse
yup sorry, knew that, typo error:angel:

kazemitsui said:
is changing the CID purely for official OTA's?
I really dont get it if youre running a ROM. heh
Click to expand...
Click to collapse
If you're on a custom ROM then you don't need to change your CID. It's only if running stock is it important

bobsie41 said:
Even to apply ota?
Click to expand...
Click to collapse
With Supercid you can't receive Official OTAs, so you have to set your cid to the One that receives updates First! for example, if your hear updates start rolling out in France for the french CID HTC_203, you just have to change your cid to HTC_203 and update via OTA, even if bootloader is unlocked, the most important for official updates is the CID!
If you're going to put supercid, that allow you to rom/firmware/ruu independantely from the CID, but not automatic official updates, just manual ones via recovery or fastboot (ruu).
Hope it clears out things
Regards

So quick question, I also have a Orange handset running 1.28.61.7... did you manage to S-off your device? ?
Just all i can see is there is no S-off for this software variant... please help.

Although when the device has a different model ID then the OTA will not install.
For example if your device has MID PN0714000 and you are trying to install OTA update 1.29.401.X then it will fail.

dobknobby said:
So quick question, I also have a Orange handset running 1.28.61.7... did you manage to S-off your device? ?
Just all i can see is there is no S-off for this software variant... please help.
Click to expand...
Click to collapse
The software variant your running does not matter.
What matters is the CID and the MID.
I've posted the sections you need to read in the thread you opened.

[Q] Trying to get the latest OTA update

Hi, I'm s-off and CID 11111111 and I'm in Canada, I flashed this
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed and every thing worked perfectly, then I changed my CID to HTC___Y13 to get the latest OTA update, when the update finished downloading I got a message saying that my HTC is running modified software or something like that and for my safty the update will not install.
What wrong here? can't I get the update this way?
Thank you...

nisayramo said:
Hi, I'm s-off and CID 11111111 and I'm in Canada, I flashed this
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed and every thing worked perfectly, then I changed my CID to HTC___Y13 to get the latest OTA update, when the update finished downloading I got a message saying that my HTC is running modified software or something like that and for my safty the update will not install.
What wrong here? can't I get the update this way?
Thank you...
Click to expand...
Click to collapse
at the very least, its because you have a custom recovery. Thats why the OTA failed

Where can I download stock recovery? and if i got it what i did should work in theory right?

If after you've flashed ruu, didn't flash anything .You already have stock recovery!
Other words ,after RUU you at the stock recovery.
What your MID?
"RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed" seems for 0710000 MID.
More likely,the reason of fault OTA - you are unable to meet mid OTA update.

tash2013 said:
If after you've flashed ruu, didn't flash anything .You already have stock recovery!
Other words ,after RUU you at the stock recovery.
What your MID?
"RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed" seems for 0710000 MID.
More likely,the reason of fault OTA - you are unable to meet mid OTA update.
Click to expand...
Click to collapse
Oh, I see thank you for the help.. My MID is PN0712000

You are trying to flash the OTA to htc__y13 cid/0710000 mid on phone with 07120000 mid - it's a bad idea.
What to do?
1) You can change mid, but I strongly DO NOT advise - this is a dangerous procedure.
2) You can flash the RUU for your mid and just wait for the OTA update will come to you - it is good

tash2013 said:
You are trying to flash the OTA to htc__y13 cid/0710000 mid on phone with 07120000 mid - it's a bad idea.
What to do?
1) You can change mid, but I strongly DO NOT advise - this is a dangerous procedure.
2) You can flash the RUU for your mid and just wait for the OTA update will come to you - it is good
Click to expand...
Click to collapse
I'm trying to find An RUU for my MID can you help? and of course thank you..

nisayramo said:
I'm trying to find An RUU for my MID can you help? and of course thank you..
Click to expand...
Click to collapse
What your originally CID?
And more.. just an advise .. under your current condition (after europe RUU) do not going to s-on never.

tash2013 said:
What your originally CID?
And more.. just an advise .. under your current condition (after europe RUU) do not going to s-on never.
Click to expand...
Click to collapse
My Origianl CID is BM___001, and got it s-off for ever

Unfortunately, I don't oriented to the North American operators,and I do not know what is BM .
And therefore can't advise the exact RUU
OK, let's go through the first way, under your current state change your mid to European
type:* fastboot oem writemid PN0710000
Stop stop! Before change mid type here your : fastboot getvar all

tash2013 said:
Unfortunately, I don't oriented to the North American operators,and I do not know what is BM .
And therefore can't advise the exact RUU
OK, let's go through the first way, under your current state change your mid to European
type:* fastboot oem writemid PN0710000
Stop stop! Before change mid type here your : fastboot getvar all
Click to expand...
Click to collapse
BM is Bell Mobility

I did not find your BM RUU from here
http://forum.xda-developers.com/showthread.php?p=39588860
and here
http://www.androidfiles.org/ruu/?developer=M7
Only a nandroid backup ,but I think it is not full stock, at least a stock recovery is missing and I'm afraid something else.
Time you were already flashed by the European RUU, let will change MID to European. And you will be have completely European unbranded phone.
if you decide do it .. print here " fastboot getvar all" (without your imei) I'll check your current state.

HTC One T-MOB101 how to revert it back to stock?

I have a T-MOB101 (Germany device HTC One), and i would like to revert it back to stock and sell it.
Read all the guides here at XDA, but couldn't achieve it.
My device now is:
HBOOT 1.54.00
S-Off with SuperCID 11111111
Unlocked bootloader
ARHD 13.4 rom
There isn't any RUU for T-MOB101. I found a CWM stock Nandroid backup but for some reason CWM can't install it.
I've installed the odexed 2.24.401.1 stock rom, reverted the CID back to T-MOB101, locked the Bootloader but now it says RELOCKED instead of LOCKED. And couldn't make it S-On maybe because of the HBOOT 1.54.00?
Please, help me, i would like to sell the device and the future owner don't have any issues with the warranty.

So, unlock your bootloader, go here, download the 1.44 hboot and flash it with the guide.
After, use the revone tool to go locked and s-on

Guich said:
So, unlock your bootloader, go here, download the 1.44 hboot and flash it with the guide.
After, use the revone tool to go locked and s-on
Click to expand...
Click to collapse
Thanks for the reply Guich.
I'm kinda lost in the above thread.
1) Which Base Firmware should i download for T-MOB101 German device? I would like for it to have automatic updates for the future.
2) After that i will have to download the HBOOT 1.44.0000 Original unmodified, right?
3) In which order should i flash them? It's the same method for both Base Firmware and HBOOT?
4) Lastly, my bootloader now is unlocked with the HTC's method. How i can use the Revone to go Locked and S-On? Also, when should i change the CID to T-MOB101 from SuperCID 11111111?
Excuse me for all these questions, after almost 8 hours in front of the PC with no luck my head's gonna explode..
Thanks a bunch,
Bill

bill_viper said:
Thanks for the reply Guich.
I'm kinda lost in the above thread.
1) Which Base Firmware should i download for T-MOB101 German device? I would like for it to have automatic updates for the future.
2) After that i will have to download the HBOOT 1.44.0000 Original unmodified, right?
3) In which order should i flash them? It's the same method for both Base Firmware and HBOOT?
4) Lastly, my bootloader now is unlocked with the HTC's method. How i can use the Revone to go Locked and S-On? Also, when should i change the CID to T-MOB101 from SuperCID 11111111?
Excuse me for all these questions, after almost 8 hours in front of the PC with no luck my head's gonna explode..
Thanks a bunch,
Bill
Click to expand...
Click to collapse
1) I will advise you to transform your T-MOB phone into an unbranded phone.
So, donwload the 1.29 firmware umodified and flash this.
2) Yupp, 1.44 hboot and go s-on and locked
3) Use the guide, i will advice firmware and after hboot.
4) Yup, with 1.44 hboot you can use the revone tool for go to LOCKED and not RELOCKED and s-on
But, before go to s-on, change the cid into HTC__001.
5) If you're tired do this tomoz
p.s. If you need more help, you can contact me in pm

[Q] Downgrade HBoot/firmware for repair?

Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!

No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.

Seanie280672 said:
No that firmware isn't officially released yet, it's still in testing stages so you will have to downgrade your firmware to 5.??.401.? Lucky for you this firmware comes with hboot 1.57 however if you have flashed a modded hboot/firmware ie to remove red text, then you will need to flash an official one, just find the official firmware package and use that, it comes with the hboot inside it, if you s-on with modded firmware or hboot you will have an instant brick.
The arhd site your got the Rom from should have the firmware package too.
Click to expand...
Click to collapse
Great, thanks! I will flash the original firmware in a sec, but the most recent RUU I can find is this one: http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
And I am not sure if that is also based on hboot 1.57 and because of that, if I am able to flash this RUU. Currently I am downloading it but the download speed is terrible, I will report back after I tried.

Or are you saying that I can flash the stock firmware 5.xx.401.xx on top of the current 6.xx firmware? I thought that wouldn't be possible because I'm currently on a higher firmware version but I'll give it a shot!

If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.

Seanie280672 said:
If you are s-off, you can flash or downgrade anything, however I would personally flash the matching firmware to the ruu that you are downloading, however, the firmware and hboot will be included in the ruu and be downgraded when you run the ruu, so just run it, once it's finished and you boot the phone, you can ota up to the latest version.
Click to expand...
Click to collapse
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!

WiiiLDFARMER said:
Ah I see, thanks a lot! Still waiting for the RUU to finish, I'll download the corresponding firmware and flash it before I start the RUU. Thanks again!
Click to expand...
Click to collapse
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Once it's finished, boot the phone once and then back into bootloader and check the hboot version, if it is lower than the version you have on there now then you'll know you have stock hboot and should be safe to s-on, however like I said before, make sure your locked and tampered has gone before setting s-on (not sure if s-on is required for warranty)

Seanie280672 said:
You may have to remove the TAMPERED flag before running the ruu and also lock your bootloader, not relocked as the ruu will replace which ever recovery you ha e on your phone for the stock one, sometimes the ruu requires a locked bootloader whether s-off or s-on.
Click to expand...
Click to collapse
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?

WiiiLDFARMER said:
At the moment I don't have a tampered flag, it only says 'unlocked'. I'll try to lock the bootloader before starting the RUU. Do you know if the Tampered flag will return if I S-ON my M7 after completing the RUU?
Click to expand...
Click to collapse
Unfortunately I don't know that, there's been some reports it comes back after you s-on not after the ruu, I think it's HTC 's way of catching you out, others say it's been fine, are you sending it to HTC or your operator ?
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
However , if you've had s-off with that phone before, chances are you'll get it again, you'll just have to do whatever you did before to get it, then go back to stock again, and send it s-off.

WiiiLDFARMER said:
Hi,
I want to send my HTC One in for repair, so first I need to restore it to stock.
However, I recently updated my firmware (and hboot) to the new 4.4.3 base (http://forum.xda-developers.com/showthread.php?t=2793539) so right now I am (s-off) on hboot 1.57.0000... Is this a problem when sending it in since this firmware isn't officially released yet (or is it)? And if it is, is it possible to downgrade my hboot?
Also, must I flash the firmware WITH the red warning before going S-on and locking the bootloader again?
I have flashed the stock odexed ROM, boot.img and recovery from the ARHD site (http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html).
Thanks in advance for any help!
Click to expand...
Click to collapse
Try this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
It worked for me, returned full stock!