Related
Hello,
i have a T-Mobile flyer 3G 32gb with original HC
Build-number 3.55.111.1
baseband 20.4803.30.0822U_3822.11.08.07M2
HBoot 1.11.0011
Radio 3822.11.08.07M2
CID T-MOB101
I want to S-off and flash a custom rom but i don't know the best, the right, way to do this. So it's possible to have S-Off with this device?
I downloaded the T-Mobile RUU but with this RUU i can't downgrade to GB.
The RUU updater say Error 140 and stopped.
So what can i do for S-Off?
devil-77 said:
Hello,
i have a T-Mobile flyer 3G 32gb with original HC
Build-number 3.55.111.1
baseband 20.4803.30.0822U_3822.11.08.07M2
HBoot 1.11.0011
Radio 3822.11.08.07M2
CID T-MOB101
I want to S-off and flash a custom rom but i don't know the best, the right, way to do this. So it's possible to have S-Off with this device?
I downloaded the T-Mobile RUU but with this RUU i can't downgrade to GB.
The RUU updater say Error 140 and stopped.
So what can i do for S-Off?
Click to expand...
Click to collapse
Hey man...
I have the EXACT same flyer, everything the same... Did you manage to get it s-off and rooted back to Honeycomb?? I have read all the forums, but I actually can't find a clear solution! Lemme know please or if anybody can put it simple! Thanks!
custom rom for flyer with stock hc
These steps would help :
- unlock boot loader over htcdev
- flash cwm with fastboot
- with cwm you're able to flash any custom rom (zip files)
It worked at least on my htc evo 3D.
Hey,
I have somewhat of the same question - but remain puzzled... I unlocked the Flyer's bootloader yesterday through HTCdev, flashed a Revolutionary recovery (based on CWM) through fastboot and could then install SuperUser through an update.zip in the stock ROM.
I have mode some development on other devices, so I'm familiar with bootloaders and stuff. The forums are mostly talking about S-OFF and I don't really understand how that concerns me, because now that my stock ROM is rooted, I can do whatever I like (remove bloat etc.). I may not understand all implications of S-ON, but I know that my bootloader tells me my Flyer is S-ON.
Now, is there any problem to flash another ROM through CW Recovery? Will, for example, LeeDroid's ROM replace anything connected to 3G (I have the model running on AWS frequencies, which are quite unusual). Could I simply flash LeeDroid's ROM, then get back to my stock backup without any problem?
I guess the question is; since my bootloader is unlocked, does S-ON or OFF concern me in any way? Or is S-OFF only important for those who can't unlock their bootloaders through HTCdev?
Thanks!
(I do promise to write something up for the wiki if ever I understand
S-On means you can't flash a custom ROM through recovery or ROM Manager. You can only flash using fastboot.
Thanks!
So considering that I just tried to downgrade to Gingerbread in Windows and that I got Error 155 (which seems to be undocumented - the message was à la 'something went wrong - I don't know what'), can I restore CW recoveries through fastboot as well?
I wouldn't mind to plug the cable, and S-OFF seems like an unnecessary hassle to me... (I just want OpenVPN and from here I took as much time trying to figure that out than I would need to compile the module myself).
I guess what puzzles me is this (from the LeeDroid thread): "If you have acheived S-Off via HTCDev, you will need to extract the boot.img from the Kernel.zip and flash it via fastboot"
I don't have S-OFF. I have an unlocked bootloader.
Does that mean that if I want to switch to LeeDroid I first have to fastboot flash boot.img and then install the rest through CW recovery?
Similarly, if I want to get back to stock, I fastboot flash the boot.img from my backup and apply the rest through CW recovery?
Thus: S-ON actually only prevents the boot partition to be changed outside from fastboot?
Thanks again!
redpoint73 said:
S-On means you can't flash a custom ROM through recovery or ROM Manager. You can only flash using fastboot.
Click to expand...
Click to collapse
Hm. I just did full restore with CW recovery.
And I had already applied update.zip's with the recovery.
ADD: SOLVED. What I wrote in the post above was right. I can apply any zip file, but CW can't write boot.img. Solution: fastboot flash boot boot.img.
All the rest works. In order to get back to a backup I guess it's the same way - flash boot.img, apply the restore.
cid: TMOB010 and HBoot 1.11.0011 Please Help Soff this thing.
I have the exact same problem and I assume I need s-off to make this work like a phone. Yes? Has anybody figured this out yet?
bud.
I seemed to be in a unique position; unlocked 1.53.0007 bootloader via HTCdev and S-OFF using the wire trick, stock ROM with OTA ICS and NO ROOT!
Now, it was very easy, and I'm not saying that it's an "achievement", but I though I'd share it so that the next guy won't have to wonder if it's going to work or not...
I did it because I didn't want to mess around downgrading to GB, changing bootloaders and using custom ROMs.
Here's what I did:
I downloaded the root.zip (actually named root-OTA-ICS.zip) linked in this post:
http://forum.xda-developers.com/showthread.php?t=1732984
and placed it on the SD card.
And then I downloaded the CWM recovery image:
http://www.clockworkmod.com/rommanager/
and placed it in the same folder as fastboot.exe and adb.exe (and the required dlls, of course!)
I'm going to assume that you know what adb, fastboot and bootloader is, as you already have S-OFF and an unlocked bootloader...
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-shooteru.img
Rebooting into recovery and chose "Flash zip from card" (or something close to that)
Selected root-OTA-ICS.zip and hey presto!
One thing to notice was that Titanium Backup alerted me to a change in my Android ID, and asked if I wanted to change it back.
Thanks to those I linked to!
Were you able to unlock?
Your question makes no sense.
I'm sorry, you must have misread the post.
This thread is about rooting an already unlocked bootloader.
I used HTCdev for the unlocking and the wire trick for S-OFF.
You got clean ICS update and then unlock,root and soff? or before
EP(Y)C said:
You got clean ICS update and then unlock,root and soff? or before
Click to expand...
Click to collapse
Yes.
The phone was stock GB, upgraded OTA to ICS.
I believe I unlocked the bootloader first, but I'm not sure.
It shouldn't matter anyway, as I used HTCdev to do the unlocking.
Strange, but i was thinking i was unique
My was stock GB too. I have upgraded over OTA to ICS and got hboot 1.53.****. Stock ICS was to crappy for me, so i have decided to unlock my phone with HTCDev method and flash custom firmware(with same kernel) without doing any wire tricks or so... I have done HTCDev unlock(but must flash unlock_code.bin twice, because first time it hasn't worked). I was expected to get S-ON(right?), but on restart in bootloader it was "***UNLOCKED ***" and S-OFF. So i can flash any custom firmware, boot animation, kernels just fine. What was I'm doing wrong?
It's been awhile since I've had a chance to get back to xda, so when I saw the htc dev bootloader unlock method, I jumped at the chance to unlock my version 1.5 bootloader and be able to get root without downgrading. However, just a few days later, the Ics ota was released. I had
1. unlocked my bootloader VIA HTC dev method,
2. Flashed twrp from command prompt, and
3. Flashed Su from twrp.
In a nutshell, I had root but was on a stock 2.17 ruu (latest gingerbread ruu) and had root. In order to try to revert to stock, I used the command "fastboot oem lock" to relock my EVO (cdma) so i could ota update, because when i tried to with root, I simply was booted into twrp.
So, after locking (and also removing the recovery.img from my sdcard) my bootloader, I tried to ota, which only put me into my bootloader with a message under "relocked"(at the top of the screen in bootloader) which said "security warning". I've tried to run the 2.17 ruu when in fastboot (because it would only give me security warning otherwise) but there was pretty much no visible effect on my phone. The ruu said it ran successfully, but after booting up I still had Su, and none of my app data had been deleted. I also couldn't do a factory reset from the OS or from bootloader. If anybody could help me get to ics anything, or at least back to stock w/o root (,so i can apply the ota and go from there) it would be greatly appreciated.
As a sidenote, I haven't used the ruu.zip method (PG86IMG.ZIP).
Ryoma Echizen said:
It's been awhile since I've had a chance to get back to xda, so when I saw the htc dev bootloader unlock method, I jumped at the chance to unlock my version 1.5 bootloader and be able to get root without downgrading. However, just a few days later, the Ics ota was released. I had
1. unlocked my bootloader VIA HTC dev method,
2. Flashed twrp from command prompt, and
3. Flashed Su from twrp.
In a nutshell, I had root but was on a stock 2.17 ruu (latest gingerbread ruu) and had root. In order to try to revert to stock, I used the command "fastboot oem lock" to relock my EVO (cdma) so i could ota update, because when i tried to with root, I simply was booted into twrp.
So, after locking (and also removing the recovery.img from my sdcard) my bootloader, I tried to ota, which only put me into my bootloader with a message under "relocked"(at the top of the screen in bootloader) which said "security warning". I've tried to run the 2.17 ruu when in fastboot (because it would only give me security warning otherwise) but there was pretty much no visible effect on my phone. The ruu said it ran successfully, but after booting up I still had Su, and none of my app data had been deleted. I also couldn't do a factory reset from the OS or from bootloader. If anybody could help me get to ics anything, or at least back to stock w/o root (,so i can apply the ota and go from there) it would be greatly appreciated.
As a sidenote, I haven't used the ruu.zip method (PG86IMG.ZIP).
Click to expand...
Click to collapse
You don't need to upgrade to ics to get a custom ics rom, if that's what your asking. Reunlock, and check out the development forums and find an ics rom that works with 2.17 (eg, cool sense, meanrom, homebrew, common sense [my rom lol]). Go ahead and flash one, and enjoy ics
Stay on 2.17 though, first rule: NEVER accept ota. It's kinda rule of thumb. I learned the hard way.
Sent from my EVO 3DMA with a little "common sense"
I assume you're s-on..
You said you tried the ota and it took you to the hboot. Did it upgrade your hboot to 1.58?
I think the security warning is due to having a custom recovery (i think)
Wikd said:
I assume you're s-on..
You said you tried the ota and it took you to the hboot. Did it upgrade your hboot to 1.58?
I think the security warning is due to having a custom recovery (i think)
Click to expand...
Click to collapse
Yeah I checked out some other threads (none for the 3d though) and they said pretty much that it did have to do with the custom recovery like you said. And you are right on the other two counts, but no, it didn't upgrade me to 1.58, I'm still on 1.5.
Alright, thanks! I'll try to re-unlock using the HTC method(I'm assuming ill need to get another unlock_code.bin since the one I used isn't working anymore for some reason). I'll post again and let you know how it goes.
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !
Can anyone upload the AT&T stock recovery img? @thoughtlesskyle was awesome enough to upload the system and boot partitions here http://forum.xda-developers.com/att-one-m9/general/stock-stock-twrp-t3080499
I guess the AT&T RUU would work as well if anyone has that floating around.
THX all!
I would also really appreciate a flashable stock recovery partition!
I have a brand new HTC One M9, stock and untouched - I unlocked the bootloader, but relocked it before flashing TWRP or anything because I realized that I can have root, or stock recovery, but not both.
I'm reluctant to wipe the stock recovery image and replace it with TWRP, because I *really* want the camera OTA applied correctly when AT&T decides to push it out.
If I wipe the stock recovery, install TWRP, and install root along with a ROM - I'll lose the stock recovery, and even if I reflash a bone-stock system dump, the recovery partition will be modified so I won't be able to take the AT&T signed OTA and flash it.
I even tried to "fastboot boot twrp-recovery-2.8.6.4.img" in both bootloader and download mode to see if I can use TWRP without flashing and blowing away the stock recovery partition, but no luck.... and it seems I'm unable to backup the stock recovery partition as is unless I get root (which requires me to flash TWRP...)
You can get it here
How to bring back to STOCK ATT ROM
What are the steps to be followed to get back my device to stock rom?
I'm quite confused which files i have to keep in the TWRP and flash...
Can someone please help me in bring back my my phone to a stock ATT?
yashwanthl92 said:
What are the steps to be followed to get back my device to stock rom?
I'm quite confused which files i have to keep in the TWRP and flash...
Can someone please help me in bring back my my phone to a stock ATT?
Click to expand...
Click to collapse
You can use this guide
http://forum.xda-developers.com/showthread.php?t=3068243
[2015.04.16] Firmware flashing with Fastboot
Back to ATT Stock
But I do not have a S-OFF made on the device, or rather i would not..
[2015.04.16] Firmware flashing with Fastboot[/QUOTE]
yashwanthl92 said:
But I do not have a S-OFF made on the device, or rather i would not..
[2015.04.16] Firmware flashing with Fastboot
Click to expand...
Click to collapse
[/QUOTE] you can go here and get AT&T ruu with latest update.
I'm confused on how I can return my m9 to Full stock. I have twrp , S OFF and SuperSU.
I've downloaded RUU from http://www.htc.com/us/support/rom-downloads.html
Do I first do S-ON then launch RUU exe and it will be back to stock? Do I even need to have S-ON ? Will flashing RUU via just running it remove root AND twrp?
att HTC One M9 back to stock fully
So this is what I found after some research and was successful at resetting everything to stock:
If you are rooted, unlocked, your status on bootloader says 'modified' but you want to go back to stock. To return the phone or some other reason:
First - set your phone to S-OFF with http://theroot.ninja/index.html I know - it costs $25. I will gladly accept another way of doing it, but unaware of one.
Second - set your Software Status back to Official by visiting this thread: http://forum.xda-developers.com/one-m9/general/how-to-restore-software-status-original-t3092882
This the second step since you need to be S-OFF for it to work.
At this point you'll still have your Bootloader showing as Unlocked and of course S will be OFF.
Then do the step 2 to lock the bootloader: http://forum.xda-developers.com/one-m9/general/guide-return-m9-to-100-stock-s-off-t3091730
Then I would not do step 3, but only because I found ROM exe for my ATT one m9 here: http://www.htc.com/us/support/rom-downloads.html
It'll take 5 minutes or so to finish. This will reload your Lollipop back to factory state. It will also unroot your phone.
Then you can do S-ON by rebooting to download mode ( adb reboot download ) and running: ( fastboot oem writesecureflag 3 ). This was 'optional' step after step 7 at http://forum.xda-developers.com/one-m9/general/guide-return-m9-to-100-stock-s-off-t3091730