Ok so here is what I did
I unlocked the bootloader through HTCs site
I installed a custom recovery
I installed a custom ROM
S-ON is still there, so I wanted to downgrade to turn S-OFF unfortunately I did the dumbest thing possible and locked the bootloader again attempting to downgrade so I can use revolutionary. Now I have a security warning
I am not exactly sure what to do from this point. The phone is fully functional on a custom ROM but I have no recovery access and I want to install MIUI.
If anyone has an idea I would like to hear it. I went wrong by not downgrading and turning S-OFF before unlocking the bootloader. I just want to know how I can fix this.
Did you revert back to a locked bootloader? If so, just follow the instructions in Development for downgrading .98 bootloader.
sjpritch25 said:
Did you revert back to a locked bootloader? If so, just follow the instructions in Development for downgrading .98 bootloader.
Click to expand...
Click to collapse
Yeah it's not working :-\
It gives an error when it does the fastboot gets stuck on waiting for device, I manually reinstall the verizon rom and it goes to the black HTC screen. Finishes sending and restarts on the custom ROM I already have on there.
Phone is still locked with the security warning. Person using the phone has been using a sense rom, would really like to get rid of a the security warning :|
as long as you re-locked the bootloader you should be able to s-off. What bootloader do they have? If its .98 you will need to downgrade and s-off.
anytime I try to downgrade the phone goes into a bootloop when I run hack-vivow.cmd
if I manually boot it into the bootloader after that, the script says it's sending the files, once it's done and the phone reboots it goes back to the last ROM it was running as if I never did anything :-\
Try a different computer or account. For some reason it wouldn't allow me to run hack_vivow.cmd or whatever on mine, re installed sdk and adb on my laptop and did the drivers, made sure fastboot was off, and it ran perfectly. Now that was me being on 2.3.4 shipped with the .98 bootloader. Now on my pc I went and s-offed because for some reason on my laptop, it wouldn't recognize my device, and then I pushed the recovery and use adb all the time
Sent from my ADR6350 using XDA
Here are the details of what I am dealing with as of now:
S-ON
Custom Recovery is installed
Phone is Rooted
Bootloader is unlocked
Currently on 0.98
ROM is TSM Bullet
I cannot downgrade even if I relock the bootloader, it will install and run the last ROM that was on there. Only ROMs that are signed appear to work and I'm guessing this is because of S-ON. I need to know how I can get S-OFF or even downgrade at this point. I tried every method I could find here and nothing seems to work
you need to relock install ruu 2.3.4 with hboot .98-do this from bootloader(PG32IMG)
THEN RUN DOWNGRADE TOOL
THEN RUN REVOLUTIONARY FOR ROOT AND S-OFF
---------- Post added at 09:57 PM ---------- Previous post was at 09:41 PM ----------
If your on a custom rom you need too go back to stock or downgrade tool won't work.
Seems to be getting stuck at the command reboot fastboot oemRUU
???? download the ruu rename it PG32IMG put on the root of sdcard. make sure the file on the sdcard reads PG32IMG.zip.(exactly)then boot into bootloader, it will pick up the file and run it then ask to proceed, select volume up to continue, it should install up date. if you phone won't let you put it on your sdcard at this point either put it on another card or pull your card put it in an adapter and move to card with your computer.
---------- Post added at 10:27 PM ---------- Previous post was at 10:25 PM ----------
you don't need to use adb to do the ruu
Sorry it's locking up there on the downgrade. I am going to start on another computer and follow the instructions on downgrading. I am back to stock!
ok step one complete
---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------
make sure you put the vivow hack files on the root of C: then type cd cthe file name)
Phone rooted, S-OFF
THANK YOU!!!
YIPEE!!!!
Related
When I tried the new OTA with a new Incredible I got off of eBay (not rooted or tampered with) it kept messing up half way through and causing my phone to constantly reboot. I restored my phone but when I leave it plugged in with 3G on the OTA messes up my phone again.
I don't have root access so ES Explorer can't delete the .zip in the security folder to stop the OTA.
I've been trying to downgrade the HBOOT and get it to 2.3.3 but it won't work.
I either want it to be full stock or gain S-OFF so I can put CM9 on there. I have HBOOT .98 and can't get it to downgrade.
So, I tried following the following:
http://forum.xda-developers.com/showthread.php?t=1298990
Everything worked fine up until near the end. It says "remote: 99 unknown fail". (SEE 1ST IMAGE)
*NOTE, ERASING CACHE WILL WORK. JUST DIDN'T THIS TIME. I'VE TRIED THIS SUCCESSFULLY UP UNTIL THE REMOTE 99 FAIL*
http://www.youtube.com/watch?featur...v=CgIYFGcVimU&annotation_id=annotation_395071
It's still 2.3.4, Sense 2.1.
My phone is Unlocked but still S-ON. I can't get rid of S-ON no matter what I try and do.
See 2nd image for what my HBOOT looks like.
Can anyone tell me what I'm doing wrong and what steps I need to follow at this point?
Also, can I flash CM9 and delete bloatware even with S-ON?
Thanks!
Someone correct me if I'm wrong, but it seems like the phone was unlocked through the HTC Dev Unlock tool. Have you tried relocking using that?
Sent from my Incredible 2 using xda app-developers app
To my knowledge I didn't use that. Just what is listed on these links.
Where can iI find this program and try to relock?
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
I cant boot back into the phone.
---------- Post added at 03:10 AM ---------- Previous post was at 02:43 AM ----------
I locked the bootloader and now it just will not boot into the phone. I tried to go into recovery but it just reboots.
Did I just mess up my phone?
sjpritch25 said:
You need to relock the bootloader before pursuing s-off.
to relock bootloader
Navigate to your adb & fastboot folder
Code:
adb remount
adb reboot bootloader
fastboot devices
fastboot oem lock
Then you should be able to downgrade and s-off.
Click to expand...
Click to collapse
Thank you! I actually decided to stick with stock. The new OTA actually worked this time around so I have no issues. IF ICS ends up never coming out, I'll eventually root. I really enjoy Cyanogenmod but for now stock feels safe for me.
You have no idea how much I truly appreciate this. I've been frustrated for a week. Searching all over the internet and doing everything in my power to fix it. All it took.. was that! THANK YOU!
Your welcome...
Now I have no stock recovery. It's a phone image and a red exclamation point. It then boots e3 and says something like "E: can't open cache/recovery/command"
How can I regain stock recovery?
Sent from my ADR6350 using xda app-developers app
Download the gingerbread RUU located http://minus.com/mvivow#1
I recommend renaming before downloading it.
rename it PG32IMG
Be careful with windows because it might rename it as PG32IMG.zip.zip. It won't work.
Move it to the sdcard
reboot into bootloader and allow the update. Its a signed RUU, so it should work.
It says "Main Version is older! Update fail"
Is there a RUU yet for the latest 6.xxxx OTA version?
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked again and could use recovery, which is what I'm doing right now.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
It would be less confusing if you used the same user name on all the forums you post on.
undergone said:
I used the HTCDev tool to unlock again. At that point I was able to flash an .img of clockwork mod recovery.
When I re-locked I could no longer access Recovery. It said ***SECURITY WARNING*** and would not enter it.
I unlocked the phone again and can now use Recovery. I will stay like this I suppose.
Am I not allowed to use Recovery with a locked phone?
Also, if I leave my phone unlocked, IF and WHEN there might be an ICS OTA for the Inc 2, can I still download and install while being unlocked?
Thanks!
Click to expand...
Click to collapse
Sorry dude.
Here's what is happening now... let me re-clarify.
So I had several issues caused by the latest INC 2 OTA. After the OTA messed up my phone I followed several threads online to downgrade to 2.3.3. After I did this, I updated back to 2.3.4 and then did the new OTA. It worked.
When I did this, "recovery" disappeared in the bootloader.
I eventually unlocked my phone again and was able to flash a custom recovery.img to get clockwork mod recovery back on. Everything was going smoothly!
I then entered recovery and accidentally restored a previous backup (version 5.xxxxx which would power off due to the OTA messing it up). So I immediately did a factory reset.
After this, the Radio is 1.09.01.0312. Every time I boot up it gets stuck on the white HTC screen. I've tried clearing cache, formatting system and then doing a factory reset. It still is the same.
To my knowledge this current radio is the radio for the new OTA (6.xxxxxx). My phone thinks it's software is still 5.xxxxxx due to the accidental restore.
I guess the radio I need ends in .1111. Would not having this radio cause this issue? I downloaded the radio but it says I have to be S-OFF to install it.
I am currently unlocked and S-ON.
Am I screwed or is there anything I can do to fix this?
I can only Fastboot and use CMD prompts. I don't even care if it's a custom rom at this point. Anything I can do to restore the phone.
Please and thank you.
EDIT: Also, PG32IMG files will not work. If I go to manually install it says E: Can't open sdcard/PG32IMG.zip (BAD)
Nor will it go through when I boot it up in the bootloader. I tried this for the version 5.xxxxxx. Do I need to wait for a 6.xxxxxx officiall RUU PG32IMG to come out? I haven't seen one yet.
when you see the red exclamation point press power button and volume up at same time, will put you in stock recovery
Is there ANYONE that can possibly help be fix my phone? I'm still stuck in the white HTC boot screen.
I can only load up in the bootloader.
***UNLOCKED***
VIVO_W XB SHIP S-ON RL
RADIO-01.09.01.0312
eMMC-boot
I need to install the latest software. Is there a RUU yet for the latest 6.xxxx software yet as a PG32IMG?
Any steps to successfully do this would be appreciated.
Could someone with the stock software do a backup, zip the file and send it to me? that way I could put it in the sd/clockworkrecovery/backup and try to make it work.
Thank you.
EDIT: ***HERE IS THE FIX THAT WORKED FOR ME***
Here is how I fixed it: I suggest all others with my issue try this...
Flash the boot.img from this rom: http://forum.xda-developers.com/showthread.php?t=1737494
THEN went into recovery > factory reset > clear cache > wipe dalvik > install zip from SD > install
If you need addition details, how to flash, etc. they can be found here (http://forum.xda-developers.com/showthread.php?p=28262673#post28262673) where I was also given help.
I'm user "telecastertunes" on there.
Good luck!
Hy everybody,
My hox is like a surprise box.
Yesterday i could not do anything because of empty battery but i fixed it.
And today fastboot seems not to work correctly.
For example, if i try to flash recovery i doesn t change anything. It shows writing sos partition okay and succes.
And when i go to recovery it s stays with the same recovery.The same trouble with flashing boot.
The i try to install a rom over cwm 6 it shows okay but i get stuck a rom bootscreen. If i try to mount usb, it works
then i put a new rom on it after unmounting rom isn t on the internal memory.If i erase anything on my memory over
windows folder and files disapear but on unmouting nothing was deleted.
It s like i dont have any rigths.
I flashed to hboot 1.39 got no trouble and cid is HTC_102.
Does anybody got a solution ?
Can you lock your bootloader?
Try running a RUU. That oughta reset any problems with partition permissions.
Sent from my One X
TToivanen said:
Can you lock your bootloader?
Try running a RUU. That oughta reset any problems with partition permissions.
Sent from my One X
Click to expand...
Click to collapse
Nope when i try to lock it reboots and starts rom instead of going to bootloader and showing relocked
Bloodbreed said:
Nope when i try to lock it reboots and starts rom instead of going to bootloader and showing relocked
Click to expand...
Click to collapse
what is also strange is that i can t erase boot or recovery
is there anyway over gparted to fix partition rights ?
Try using a ruu
Guich said:
Try using a ruu
Click to expand...
Click to collapse
Not sure if it works because i never could install one .
On xda i can t find any working RUU and i think i need a 3.14 RUU do you now
where i can find it please
You can't use RUU if you can't lock the bootloader.
Anyways RUUs here: http://forum.xda-developers.com/showthread.php?t=2104672
Sent from my One X
TToivanen said:
You can't use RUU if you can't lock the bootloader.
Anyways RUUs here: http://forum.xda-developers.com/showthread.php?t=2104672
Sent from my One X
Click to expand...
Click to collapse
that s what i was thinking
Bloodbreed said:
that s what i was thinking
Click to expand...
Click to collapse
AndI guess there is still no apx mode hack tool where i can flash rom from beginning ?
What ROM/kernel have you been running prior to the problem?
---------- Post added at 09:56 PM ---------- Previous post was at 09:52 PM ----------
Nevermind, I've seen your posts in Trip's kernel thread. Your HOX is bricked. No solution until we can achieve S-off. Until then you can either wait or send it to repair. You can risk and try to brick your bootloader by trying to relock the bootloader and running RUU (more likely to "avoid" the void warranty so to say but also more likely to be charged for more should they discover you unlocked the bootloader), or just send it as-is.
BlueSingA said:
What ROM/kernel have you been running prior to the problem?
---------- Post added at 09:56 PM ---------- Previous post was at 09:52 PM ----------
Nevermind, I've seen your posts in Trip's kernel thread. Your HOX is bricked. No solution until we can achieve S-off. Until then you can either wait or send it to repair. You can risk and try to brick your bootloader by trying to relock the bootloader and running RUU (more likely to "avoid" the void warranty so to say but also more likely to be charged for more should they discover you unlocked the bootloader), or just send it as-is.
Click to expand...
Click to collapse
Thanks for the response.
I m not sure about the bricked device since it boots to android (okay i can not acces to android the user way) but
device seems to connect perfectly to pc with adb and i guess it s just a partition permission that need to be reseted.
Isn t there a way over linux to achieve that?
Hello all, I've been a lurker in the shadows for many months using the amazing expertise on this board for my different devices. So here I am needing help and hence my first post.
I basically bought a Verizon HTC One and now have issues that I need to return the phone for warranty. I used the rumrunner process to unlock my bootloader and s-off. I have proceeded to delete most of the bloatware (probably not an issue but just trying to give as much of the backstory as possible) but I have kept the phone stock other than that (no custom ROMs). I did install Clockwork recovery 6.0.4.4 (not touch). When my phone reboots, I do have the red text at the bottom. I believe that is all really. I have attached a pic of my bootloader screen if that helps. I just need to know exactly what steps to follow to return it to stock out of the box. Sorry if this has been answered before but there are so many different threads with what seems like other issues. You guys don't know how much I appreciate the help in advance, Thanks!
I am in the exact same situation...so far from what I can tell the problem is getting stock recovery and being able to get s-on back
---------- Post added at 04:57 PM ---------- Previous post was at 04:27 PM ----------
I am in the exact same situation...so far from what I can tell the problem is getting stock recovery and being able to get s-on back
If you guys have an unlocked bootloader you can pull stock recovery.IMG out of the decrypted RUU zarboz posted and that will get you back to stock recovery. You need to have the fastboot and adb files from htcdev. Just copy that recovery.img to your fastboot directory and use (dont type cmd: ) cmd: fastboot flash recovery recovery.img. Once you have stock recovery and are absolutely dead set on sending the phone in for warranty repairs you can flash that decrypted RUU via RUU mode. The instructions for flashing the RUU are in Zarboz's thread. Once you flash that there is a tool that gets rid of the red lettering and spoofs the system into saying s-on even if it isn't.
OR once you get back to stock recovery you can download the signed zip I tracked down. I'll post that link once I get home.
Sent from my One using XDA Premium 4 mobile app
Guess I am just lost right now...
Where do I find these fastboot and adb and get them on the phone..
Tracked down Zarboz's thread but no working links...
Give this a try....http://forum.xda-developers.com/showthread.php?t=2475216&highlight=s-on
MunkyK77 said:
Guess I am just lost right now...
Where do I find these fastboot and adb and get them on the phone..
Tracked down Zarboz's thread but no working links...
Click to expand...
Click to collapse
Really? Odd. As far as the adb and fastboot files get on HTCDev and download the SDK. HTCDev actually gives you the instructions on the site.
Hi,
I have rooted my phone ,s-off etc, and I have TWRP.
I am unable to install the update, phone goes to recovery, stops there.
Is there anyway I can download the update and flash it manually , or do i have to go back to stock recovery?
thanks
leonzon said:
Hi,
I have rooted my phone ,s-off etc, and I have TWRP.
I am unable to install the update, phone goes to recovery, stops there.
Is there anyway I can download the update and flash it manually , or do i have to go back to stock recovery?
thanks
Click to expand...
Click to collapse
I'm not an expert . But I think you can't flash stock Rom from custom recovery. You must do it with Adb commands or what they like to call flash in fastboot mode. And for getting official firmware updates from HTC you need to setup stock recovery. I dunno but you may have to lock boot loader and S-ON too. But not sure. As I said, I'm not an expert
leonzon said:
Hi,
I have rooted my phone ,s-off etc, and I have TWRP.
I am unable to install the update, phone goes to recovery, stops there.
Is there anyway I can download the update and flash it manually , or do i have to go back to stock recovery?
thanks
Click to expand...
Click to collapse
You need a stock recovery to do OTA updates, won't work with custom recovery.
COLLECTION of Stock Backups See if you can find your stock recovery in that thread. Flash it and then you should be good to go.
---------- Post added at 06:57 PM ---------- Previous post was at 06:46 PM ----------
Saikat.mondol1 said:
I'm not an expert . But I think you can't flash stock Rom from custom recovery. You must do it with Adb commands or what they like to call flash in fastboot mode. And for getting official firmware updates from HTC you need to setup stock recovery. I dunno but you may have to lock boot loader and S-ON too. But not sure. As I said, I'm not an expert
Click to expand...
Click to collapse
No, if he's S-OFF there is no need to lock bootloader or to go S-ON.
He can just download the recovery stock .img file and flash it through command prompt. When he's done and the phone restarted he should get the OTA update.
Only issue he might run into, if he's rooted he'll lose root access and will have to reroot, it happened to me, but it's not a major issue though.
BerndM14 said:
You need a stock recovery to do OTA updates, won't work with custom recovery.
COLLECTION of Stock Backups See if you can find your stock recovery in that thread. Flash it and then you should be good to go.
---------- Post added at 06:57 PM ---------- Previous post was at 06:46 PM ----------
No, if he's S-OFF there is no need to lock bootloader or to go S-ON.
He can just download the recovery stock .img file and flash it through command prompt. When he's done and the phone restarted he should get the OTA update.
Only issue he might run into, if he's rooted he'll lose root access and will have to reroot, it happened to me, but it's not a major issue though.
Click to expand...
Click to collapse
Thanks for the basic outline. Would you be willing to give step by step instructions? I always get nervous when I have to do multiple flashing, rerooting, etc. . .
Michael833 said:
Thanks for the basic outline. Would you be willing to give step by step instructions? I always get nervous when I have to do multiple flashing, rerooting, etc. . .
Click to expand...
Click to collapse
Instructions for? To flash back stock recovery?
1. Download the recovery from the link provided (Make sure it's the correct recovery, correct base number etc)
2. Place the downloaded recovery .img file in the adb folder where fastboot.exe is (by default it'll be in the platform-tools folder) - Though if you did a custom recovery you're probably already familiar with this.
3. Hold shift and right click anywhere in the white area of the folder > go to "open command prompt/window here"
4. Plug usb cable into device and connect up to computer (All familiar surely if you did custom recovery)
5. Commands:
a) adb devices ... to check if device is connected, should see serial number of device.
b) adb reboot bootloader
c) fastboot flash recovery name_of_recovery.img
d) fastboot reboot
Done.
Once the device restarted you should get the prompt for the OTA update(Depending on settings of course), you can then do OTA update.
To get mainversion number for the recovery you need. Just go to software information(in settings menu > about > software information) and check for OS version number or connect device to computer, reboot into bootloader adb reboot bootloader then type fastboot getvar version-main to see main version for device.
BerndM14 said:
No, if he's S-OFF there is no need to lock bootloader or to go S-ON.
He can just download the recovery stock .img file and flash it through command prompt. When he's done and the phone restarted he should get the OTA update.
Only issue he might run into, if he's rooted he'll lose root access and will have to reroot, it happened to me, but it's not a major issue though.
Click to expand...
Click to collapse
Actually, I forgot that. I need to lock boot loader if I'm S-ON but don't need if S-Off
Hello,
I was trying to install the Bad Boyz Sprint ONE M8 ROM 6.0 Sense 7 v4.0 one of the requirements was that i should update my firmware to 6.20.651.3 so I did, with the hboot method, everything said ok ok but after rebooting I get a black screen after the HTC logo, can anybody please help me I think i bricked it I tried getting in recovery but doest work, with tried with fastboot tried RUU and FUU but I get an error related that I cant reach my cellphone from my computer. help me please
Thanks!
are you S-off with your htc one m8?
you cant flash RUU when you are S-ON
are you able to go in fastboot mode?
the old method to recover soft bricked of old htc phone was to push recovery using fastboot drivers from CMD. it was quick method.
1st you have to tell me are you S-OFF or S-ON?
saiyansection said:
are you S-off with your htc one m8?
you cant flash RUU when you are S-ON
Click to expand...
Click to collapse
This is false. A signed RUU meant for your CID, will flash fine with s-on, as long as the bootloader is LOCKED or RELOCKED.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
x3r0k said:
one of the requirements was that i should update my firmware to 6.20.651.3 so I did, with the hboot method
Click to expand...
Click to collapse
What exactly did you flash (full file name) and where did you get it from?
---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------
x3r0k said:
after rebooting I get a black screen after the HTC logo
Click to expand...
Click to collapse
Is the phone powered off, or does it seem to be on, just with nothing on the display?
If powered off, try holding power + Vol down for a minute or so, to see if you can get into bootloader.
Hi, thanks to everybody, but i solved the issue. I let my battery drain and then I charged it for a moment and turned the cellphone with Power and Vol -, I got in fastboot instaled twrp and then installed the rom and everything works fine now, thanks
My cellphone is S-OFF
The firmware i installed was 6.20.651.3 Signed Full Firmware...(fastboot flashable): androidfilehost.com/?fid=24391638059060264
x3r0k said:
The firmware i installed was 6.20.651.3 Signed Full Firmware...(fastboot flashable): androidfilehost.com/?fid=24391638059060264
Click to expand...
Click to collapse
Not booting after flashing a full, signed firmware is normal and expected. See on the following firmware thread:
http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
Which reads:
- FullStock Wipe ZIP/FUU: this type of zip also re-flashes the /data partition with HTC’s DZDATA files (meaning you lose everything on your internal SDCARD). Also replaces the Kernel, Ramdisk, recovery and Splash1 with latest stock images! The /system partition will not be touched. (Else this would be a RUU, not a FUU). Phone will NOT boot after using this! Be sure to put a ROM onto your EXTERNAL SD before proceeding with a FullWipe ZIP! Else you can also ADB push a ROM in recovery mode after fastboot reflashing a recovery.
So flashing the ROM was the right thing to to. Nice work figuring it out.
redpoint73 said:
This is false. A signed RUU meant for your CID, will flash fine with s-on, as long as the bootloader is LOCKED or RELOCKED.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
What exactly did you flash (full file name) and where did you get it from?
---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------
Is the phone powered off, or does it seem to be on, just with nothing on the display?
If powered off, try holding power + Vol down for a minute or so, to see if you can get into bootloader.
Click to expand...
Click to collapse
redpoint ,can you clear one thing here? can you achieve BOOTLOADER RELCOK w/o S-OFF, i have already read forums on XDA that one cannot relock bootloader while S-ON
and can you flash RUU on S-ON? if am false can you post links here proving that you are true?
saiyansection said:
redpoint ,can you clear one thing here? can you achieve BOOTLOADER RELCOK w/o S-OFF, i have already read forums on XDA that one cannot relock bootloader while S-ON
Click to expand...
Click to collapse
You can easily make the bootloader RELOCKED with a single fastboot command: fastboot oem lock
To make the phone LOCKED (for instance, warranty purposes) you need to have s-off.
saiyansection said:
and can you flash RUU on S-ON? if am false can you post links here proving that you are true?
Click to expand...
Click to collapse
Yes, you can flash RUU fine with the bootloader RELOCKED (after its been UNLOCKED) and s-on. RUU will run with bootloader LOCKED or RELOCKED. It also has to be the RUU for your devices CID,MID (can only change CID and MID with s-off); and also has to be an RUU of same version or later (no "downgrading" using an older RUU unless you have s-off).
In short, running the right version RUU is fine with s-on, as long as the bootloader is LOCKED or RELOCKED.