Database Info

Anyone notice the MT4GS Bootloader Unlockable?

http://htcdev.com/bootloader/
Not looked to see if it is the current ROM released recently...since just came available I would hope so....hopefully this is good news for folks....

I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.

nice find, it'll make for a nice xmas gift for people with the latest ota

doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
did you have S-ON or S-OFF at the time?

jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
And are you using the latest update or the previous stock ROM?...

beezie916 said:
http://htcdev.com/bootloader/
Not looked to see if it is the current ROM released recently...since just came available I would hope so....hopefully this is good news for folks....
Click to expand...
Click to collapse
Yeah I noticed earlier
http://phandroid.com/2011/12/26/htc...-4g-slide-now-officially-unlockable-from-htc/

jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
beezie916 said:
And are you using the latest update or the previous stock ROM?...
Click to expand...
Click to collapse
I was using my 2nd MT4GS which I had done nothing with since I got that one. It is fresh from the box and had the new OTA update on it (I updated it myself like an hour before I tried this). I no better then to use the MT4GS that I currently use as my everyday device which does have S-Off.

And now HTC knows which phones to not honor warranty claims from.
Sent via smoke signal.

doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
Same thing... I got my unlock_code.bin file, flashed it, and didn't get the "are you sure" screen.
There doesn't seem to be any way to contact HTC about this either..?

jonnycat26 said:
Same thing... I got my unlock_code.bin file, flashed it, and didn't get the "are you sure" screen.
There doesn't seem to be any way to contact HTC about this either..?
Click to expand...
Click to collapse
Can you confirm your current bootloader version?
Sent from my NRGZ'D Sensation 4G!

jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
i am getting the same result, the unlock screen does not show up on the phone. i am on the new locked HBOOT, but i have S-OFF from before....

akapaul26 said:
can you confirm your current bootloader version?
Sent from my nrgz'd sensation 4g!
Click to expand...
Click to collapse
hboot 1-45.0013

doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
I am having same results with hboot 1-45.0013 S-on stock. Hopefully revolutionary gets a hold of this soon!

akapaul26 said:
I am having same results with hboot 1-45.0013 S-on stock.
Click to expand...
Click to collapse
This is very weird.
That's the hboot included in the latest OTA update, which this tool claims to support. I'd hate to think HTC made a mistake in listing our phone....

jonnycat26 said:
This is very weird.
That's the hboot included in the latest OTA update, which this tool claims to support. I'd hate to think HTC made a mistake in listing our phone....
Click to expand...
Click to collapse
I know, but everything works till that point?......

akapaul26 said:
I know, but everything works till that point?......
Click to expand...
Click to collapse
I'm not sure, but I think the tool would work on any HTC phone, but the token would only be accepted if the HBOOT on the phone worked with it.
Just a guess tho...

perhaps there is a glitch that they didn't catch before announcing support for our new HBOOT? a glitch that hopefully they will fix soon...

yogi2010 said:
perhaps there is a glitch that they didn't catch before announcing support for our new HBOOT? a glitch that hopefully they will fix soon...
Click to expand...
Click to collapse
I've sent an email to the support link that's listed in the email with the unlock file. Or at least, I think I have, they don't actually confirm that you've sent a message when you hit send.
If I get any response from them, I'll share it here.

My experience with the new OTA
I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.

Jaytex24 said:
I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.
Click to expand...
Click to collapse
If Revolutionary worked the way it was supposed to, it wouldn't be locked.

I just unlocked bootloader on OTA...

This may be old news, but i followed these directions and got bootloader unlocked... now i just need to figure out s-off
http://forum.xda-developers.com/showthread.php?t=1426179

Nice find...now you should be able to root with Mr root or revolutionary

Revolutionary says I'm not supported.... ;(
Sent from my myTouch_4G_Slide using XDA App

(I will try) and make a script that downgrades your boot loader for compaitability

xmc wildchild22 said:
Nice find...now you should be able to root with Mr root or revolutionary
Click to expand...
Click to collapse
I am going to see if mr. root can help. I haven't tried your tools yet... anything I need to know before i do?

Well mr root is highly based off revolutionary's code, just tweaked to my liking....so I I doubt it will say you compaitable.....however a try won't hurt. ..but if not ill start work on a downgrade tool

Just says my bootloader is not compatable... Downgrading would be great.... I tried flashing a recovery file to backdoor it but came back as " older than current" and stopped...
Sent from my myTouch_4G_Slide using XDA App

are you able to install cwm recovery through fastboot?

nlarge said:
Just says my bootloader is not compatable... Downgrading would be great.... I tried flashing a recovery file to backdoor it but came back as " older than current" and stopped...
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
not much helpful, but on htc g2 in a similar situation, when root was done, next step was to push some changes to the partition where the Version number was stored. After that downgrading was possible the way you tried, and after that the S-Off tool worked. But as of now, i think there's no information how to cheat the version in the partition which it contains, or even which that partition is. Or maybe someone already knows this?

Then maybe we try a dd if= command on the right partition to overwrite it?

I'm not sure how you got this to work, because nobody else with the OTA has...
However, if you've gotten it to work, you can root just by flashing a superuser image from: http://androidsu.com/superuser/
You won't have S-Off, but I'm not sure of the appeal of S-Off, to be honest. The only thing you can't do with the HTC tool is flash radio files and the like.

I only tried by placing the pdsumthin.zip on SD card and it wouldn't allow it...
Theoretically an unlocked bootloader should allow that... Even if s-on

nlarge said:
I only tried by placing the pdsumthin.zip on SD card and it wouldn't allow it...
Theoretically an unlocked bootloader should allow that... Even if s-on
Click to expand...
Click to collapse
Your bootloader is still locked.
EDIT: in the unlikely event it is unlocked, you'll need to flash a custom recovery before flashing root. There's a guide somewhere on xda that explains all this.

Bootlader even says unlocked at the top... So I am free there...

nlarge said:
Bootlader even says unlocked at the top... So I am free there...
Click to expand...
Click to collapse
You found nothing. We've known about this for a while now and is "officially" (HTC) sanctioned, hence it being THEIR WEBSITE AND INSTRUCTIONS.
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done (don't ask how, the instructions on doing this are EVERYWHERE, including google's dev site -- you can figure it out yourself with google....), you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
There is NO NEED for any kind of downgrade.
Edit: And do change your avatar... this is a hacker site, not a sex dating site. Nobody here is interested in seeing that.

Well... No one has been able to unlock it as of when I posted... It was failing... I will try flashing with fastboot... As long as I can use titanium afterwards, s-off isn't that important

Why is the 4gs community so on edge? No one was ever this rude with 4G or any other HTC forum

nlarge said:
Well... No one has been able to unlock it as of when I posted... It was failing... I will try flashing with fastboot... As long as I can use titanium afterwards, s-off isn't that important
Click to expand...
Click to collapse
I don't believe that's correct. I believe the issue is that the official HTC Bootloader Unlock process will not work -- and here's the key factor -- on devices that have already used the Revolution S-OFF procedure. I'm absolutely certain that people before you (who had not used Revolutionary) have successfully unlocked their bootloader via HTC's walkthrough.
nlarge said:
Why is the 4gs community so on edge? No one was ever this rude with 4G or any other HTC forum
Click to expand...
Click to collapse
Maybe it's because...
You created two threads that have nothing to do with doubleshot development
You didn't even check the General forum to see if there was an active thread about this (there is)
You can't even follow the rooting instructions posted in a thread on this very subject
As dhkr234 points out, all you need to do is flash the recovery zip and then flash the superuser zip. Just please try that. And then change your avatar.

HebrewToYou: I don't believe that's correct. I believe the issue is that the official HTC Bootloader Unlock process will not work -- and here's the key factor -- on devices that have already used the Revolution S-OFF procedure.[
I have been reading that it just kept hanging for everyone even with s-on... that is why I posted that I unlocked... I dont believe flashing recovery will work(yes i know how and tried zip method first).
What is the problem with my avatar? In the year that I have been on the MT4G thread no one has ever once complained about it... why you?
I'm not trying to be rude, I really just want to know why after all this time is it a problem?

ok, unlocked, SU and clockwork recovery all on board.. just stuck at S-on... directories are still read only, and I really would like to be able to use titanium!! but I am closer!!

[Q] Steps to install CleanROM 6.5?

I have recently restored my phone back to stock rom due to a soft-brick.
I need a step by step approach to help me install CleanROM 6.5 into my HTC One X (AT&T).
The CleanROM 6.5 thread is here: http://forum.xda-developers.com/showthread.php?t=1655011
The steps in the thread are too vague and general for me.
This is my phone's software information:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.85.502.3 710RD
HTC SDK API level: 4.11
HTC Extension version: HTC Extension_403_1_GA_4
More: Baseband, Kernel version, etc.
-I have CleanROM 6.5.zip downloaded
-I have my phone rooted using the approach from here: http://forum.xda-developers.com/showthread.php?t=1709424
-I have tried following the steps from threads in the Development section and I'm not entirely sure whether what to do next in my case
What are my next steps to installing CleanROM 6.5? Please provide step-by-step instructions as I don't want to mess up. Thanks!

synconclick said:
I have recently restored my phone back to stock rom due to a soft-brick.
I need a step by step approach to help me install CleanROM 6.5 into my HTC One X (AT&T).
The CleanROM 6.5 thread is here: http://forum.xda-developers.com/showthread.php?t=1655011
This is my phone's software information:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.85.502.3 710RD
HTC SDK API level: 4.11
HTC Extension version: HTC Extension_403_1_GA_4
More: Baseband, Kernel version, etc.
-I have CleanROM 6.5.zip downloaded
-I have my phone rooted using the approach from here: http://forum.xda-developers.com/showthread.php?t=1709424
-I have tried following the steps from threads in the Development section and I'm not entirely sure whether what to do next in my case
What are my next steps to installing CleanROM 6.5? Please provide step-by-step instructions as I don't want to mess up. Thanks!
Click to expand...
Click to collapse
Troll?

exad said:
Troll?
Click to expand...
Click to collapse
I'm not trolling. I seriously need help. Tell me what I'm doing inappropriate and I will fix it.

synconclick said:
I'm not trolling. I seriously need help. Tell me what I'm doing inappropriate and I will fix it.
Click to expand...
Click to collapse
Is your bootloader locked or unlocked?
S-ON or S-OFF?
Before we continue, I will advise you that the fact you need me to make out a step by step guide for you means you should remain stock. Please do not take this advice lightly. I am very serious and I am not trying to insult you or make myself seem superior to you or keep the XDA community exclusive (all of which I've been accused of when offering this advice). You should really read and understand before you do something like this because when something goes wrong, and something WILL go wrong, there's no guaranty anyone will be around to help you.
If you want to continue, just answer those two questions above. I'll help you but just remember, I warned you

exad said:
Is your bootloader locked or unlocked?
S-ON or S-OFF?
Before we continue, I will advise you that the fact you need me to make out a step by step guide for you means you should remain stock. Please do not take this advice lightly. I am very serious and I am not trying to insult you or make myself seem superior to you or keep the XDA community exclusive (all of which I've been accused of when offering this advice). You should really read and understand before you do something like this because when something goes wrong, and something WILL go wrong, there's no guaranty anyone will be around to help you.
If you want to continue, just answer those two questions above. I'll help you but just remember, I warned you
Click to expand...
Click to collapse
bootloader is relocked
as for S-ON or S-OFF, I don't understand. How do I check?
I've been trying to read and understand all this, but I have a feeling I've been reading wrong threads. If there's any links for a complete understanding of all this, that'd be nice.

synconclick said:
bootloader is relocked
as for S-ON or S-OFF, I don't understand. How do I check?
I've been trying to read and understand all this, but I have a feeling I've been reading wrong threads. If there's any links for a complete understanding of all this, that'd be nice.
Click to expand...
Click to collapse
S-On or S-oFF will be in your bootloader screen.
SInce you're relocked you'll have to unlock the bootloader again first. the unlock_code.bin should work again if you still have the one you got when you first unlocked the bootloader. Do you still have the unlock_code.bin?

exad said:
S-On or S-oFF will be in your bootloader screen.
SInce you're relocked you'll have to unlock the bootloader again first. the unlock_code.bin should work again if you still have the one you got when you first unlocked the bootloader. Do you still have the unlock_code.bin?
Click to expand...
Click to collapse
It says EVITA PVT SHIP S-ON RL.
No, I do not have the unlock_code.bin

synconclick said:
It says EVITA PVT SHIP S-ON RL.
No, I do not have the unlock_code.bin
Click to expand...
Click to collapse
Ok.. is your CID still 11111111
if you don't know boot to bootloader/fastboot and do:
fastboot oem readcid
Or
fastboot getvar cid

exad said:
Ok.. is your CID still 11111111
if you don't know boot to bootloader/fastboot and do:
fastboot oem readcid
Or
fastboot getvar cid
Click to expand...
Click to collapse
Yes

So the first step is to go to htcdev.com and get a new unlock_code.bin so you can unlock the bootloader.
Htcdev.com has all the instructions to get the unlock_code.bin
Once you receive it you'll want to put the unlock_code.bin in your fastboot folder, boot your phone to bootloader/fastboot and do:
fastboot flash unlocktoken Unlock_code.bin
Then select unlock bootloader in your phones screen.
Then verify that it worked in bootloader. If it didn't (sometimes it doesn't work right away) press and hold power to simulate a battery pull, when the screen goes black after capacitive buttons blink a bunch of times, let go of power, press and hold volume down until the bootloader comes up and the try again. It should work that time.
Once the bootloader is unlocked post here and I'll guide you through the rest.
Sent from my HTC One X using xda app-developers app

exad said:
So the first step is to go to htcdev.com and get a new unlock_code.bin so you can unlock the bootloader.
Htcdev.com has all the instructions to get the unlock_code.bin
Once you receive it you'll want to put the unlock_code.bin in your fastboot folder, boot your phone to bootloader/fastboot and do:
fastboot flash unlocktoken Unlock_code.bin
Then select unlock bootloader in your phones screen.
Then verify that it worked in bootloader. If it didn't (sometimes it doesn't work right away) press and hold power to simulate a battery pull, when the screen goes black after capacitive buttons blink a bunch of times, let go of power, press and hold volume down until the bootloader comes up and the try again. It should work that time.
Once the bootloader is unlocked post here and I'll guide you through the rest.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Do I select All Other Supported Models on this page? http://www.htcdev.com/bootloader/

Yes
Sent from my HTC One X using xda app-developers app

Got it. Successfully unlocked

Good. Next you'll want to download twrp 2.3.3.1 from goo.Im
Then check md5 to make sure the download is not corrupt. Google md5 checker if you need one.
Then put it in your fastboot folder. Boot to bootloader/fastboot
Fastboot flash recovery twrp2.3.3.1filename.img
Fastboot erase cache
Fastboot reboot bootloader
Select recovery from bootloader screen on your phone.
Mount usb storage in twrp with your phone connected to the pc.
Copy your Rom to your phone
Unmount your phone usb storage
Select wipe in twrp
Wipe cache, dalvik, system, factory reset
Go to install in twrp
Select your Rom.
Follow procedure on phone screen
Reboot phone when flash successful.
Because your hboot is under 1.14 that is all. If it was 1.14 or higher you would have to extract the boot.img from the Rom and fastboot flash boot boot.img
Also with s-on never ruu or ota to 3.18 or you will brick. Installing roms based on 3.18 is fine though.
Sent from my HTC One X using xda app-developers app

exad said:
Good. Next you'll want to download twrp 2.3.3.1 from goo.Im
Then check md5 to make sure the download is not corrupt. Google md5 checker if you need one.
Then put it in your fastboot folder. Boot to bootloader/fastboot
Fastboot flash recovery twrp2.3.3.1filename.img
Fastboot erase cache
Fastboot reboot bootloader
Select recovery from bootloader screen on your phone.
Mount usb storage in twrp with your phone connected to the pc.
Copy your Rom to your phone
Unmount your phone usb storage
Select wipe in twrp
Wipe cache, dalvik, system, factory reset
Go to install in twrp
Select your Rom.
Follow procedure on phone screen
Reboot phone when flash successful.
Because your hboot is under 1.14 that is all. If it was 1.14 or higher you would have to extract the boot.img from the Rom and fastboot flash boot boot.img
Also with s-on never ruu or ota to 3.18 or you will brick. Installing roms based on 3.18 is fine though.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which TWRP is correct to download. I searched up twrp 2.3.3.1 from goo.lm and got a list of options

synconclick said:
I'm not sure which TWRP is correct to download. I searched up twrp 2.3.3.1 from goo.lm and got a list of options
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img

mebyUni can
ronnie498 said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Click to expand...
Click to collapse
I tried verifying with MD5 Check and it says the codes do not match.
Also, when I tried downloading from the link, I get
"We are currently experiencing difficulties with one or more of our distribution servers. Please hang tight for this to get resolved"

synconclick said:
I tried verifying with MD5 Check and it says the codes do not match.
Also, when I tried downloading from the link, I get
"We are currently experiencing difficulties with one or more of our distribution servers. Please hang tight for this to get resolved"
Click to expand...
Click to collapse
You have a message

Goo.Im link seems to be up right now
Sent from my HTC One X using xda app-developers app

ronnie498 said:
You have a message
Click to expand...
Click to collapse
Thank you! I downloaded the file now. But what about the problem from MD5 Check?

[Q] S-OFF F/W 3.14.531.17 (T-MOB) possible?

I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?

Bump
Sent from my One S using XDA Premium 4 mobile app

My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?

bump

Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.

evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.

Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.

pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app

havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.

Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.

tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!

So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.

I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks

pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755

[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.

[Q] Follow-up: Rooting and S-OFF

So a while ago I made a few posts about my phone (I soft bricked it) then finally was able to root it with S-on. Then I couldn't get S-OFF so I reverted to stock. I tried rooting it and checking forums again but nothing works.
I don't know what I am doing wrong in the rooting process.
Here is what is written on my Hboot screen:
Code:
RELOCKED
EVITA PVT SHIP S-ON RL
HBOOT-2.14.000
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:41:-1
So can I even do anything to root it with S-OFF? Stock is so slow after using custom ROMS...
Thank you in advance!

That's very confusing, do you have the at&t model? Is your bootloader locked?
Sent from my Evita

timmaaa said:
That's very confusing, do you have the at&t model? Is your bootloader locked?
Sent from my Evita
Click to expand...
Click to collapse
I too found that very confusing. But if the stats you put up are current, you definitely need to unlock the bootloader before you can flash any Roms.
Sent from my HTC One XL using XDA Premium 4 mobile app

//JavaJ said:
I too found that very confusing. But if the stats you put up are current, you definitely need to unlock the bootloader before you can flash any Roms.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The thing is I know how to unlock my boot-loader, but it's getting the S-OFF that doesn't work. I have tried a few times and for some reason that I cannot identify I can't make it work!
I have been through many forum posts here but it has been all in vain up to now. I just don't want to unlock the bootloader if I have to revert back to stock after anyways.

timmaaa said:
That's very confusing, do you have the at&t model? Is your bootloader locked?
Sent from my Evita
Click to expand...
Click to collapse
I have the Rogers version.

Have you flashed root or a custom ROM? Do you or do you not have an unlocked bootloader and SuperCID?
Sent from my Evita

timmaaa said:
Have you flashed root or a custom ROM? Do you or do you not have an unlocked bootloader and SuperCID?
Sent from my Evita
Click to expand...
Click to collapse
I cannot obtain a superCID nor S-OFF with the methods on this website that i know of. I always get an error at the end about something with my phone. Then check superCID and it shows it clearly did not change...

You didn't answer either of the questions. You need root to get SuperCID, you need a custom recovery to get root, and you need an unlocked bootloader to have a custom recovery. If you want help here you need to answer the questions that people ask.
Sent from my Evita

timmaaa said:
You didn't answer either of the questions. You need root to get SuperCID, you need a custom recovery to get root, and you need an unlocked bootloader to have a custom recovery. If you want help here you need to answer the questions that people ask.
Sent from my Evita
Click to expand...
Click to collapse
Sorry. Sorry.
I have unlocked my bootloader, I have flashed a custom recovery (TWERP), I rooted, I was able to flash roms but not able to get superCID.
I tried different roms for the xl but all would start to crash after a while, even the stable ones. I discovered the roms I like need S-OFF and since I always get an error message while obtaining the superCID, I cannot get S-OFF and therefore the roms I want.
So I reverted back to stock for the time being so I can use my phone while trying to find a solution.
Does that explain it better?

Which SuperCID method are you using?
Sent from my Evita

timmaaa said:
Which SuperCID method are you using?
Sent from my Evita
Click to expand...
Click to collapse
I used this method
http://forum.xda-developers.com/showthread.php?t=1952038

That is the 2.20 root method, it won't work. Try the hex edit method.
Sent from my Evita

timmaaa said:
That is the 2.20 root method, it won't work. Try the hex edit method.
Sent from my Evita
Click to expand...
Click to collapse
Thank you for the quick reply How dangerous is this method though?

timmaaa said:
That is the 2.20 root method, it won't work. Try the hex edit method.
Sent from my Evita
Click to expand...
Click to collapse
And just so I understand perfectly what I'm supposed to do:
Root my phone --> Install TWRP --> Flash a rom --> use the hex-editor method to obtain CID --> S-OFF --> Flash the S-OFF rom

LimesAreOranges said:
Thank you for the quick reply How dangerous is this method though?
Click to expand...
Click to collapse
It isn't dangerous if you follow the instructions exactly.
LimesAreOranges said:
And just so I understand perfectly what I'm supposed to do:
Root my phone --> Install TWRP --> Flash a rom --> use the hex-editor method to obtain CID --> S-OFF --> Flash the S-OFF rom
Click to expand...
Click to collapse
Unlock your bootloader > install TWRP > flash superuser or rooted ROM to get root > hex edit your CID > get s-off > flash whatever you want.
Sent from my Evita

timmaaa said:
It isn't dangerous if you follow the instructions exactly.
Unlock your bootloader > install TWRP > flash superuser or rooted ROM to get root > hex edit your CID > get s-off > flash whatever you want.
Sent from my Evita
Click to expand...
Click to collapse
I have just finished unlocking the bootloader and rooting the phone. Everything works fine as of now.
I have encountered one error though : When I use the command prompt within the adb shell and retrieve the file, it has next to nothing in it and has the wrong name. It says it should be named "mmcblk0p4" while mine is named "nmdsdcid"...
http://i.imgur.com/ebkcMVo.png
I followed all the steps... :/

The imgur link above didnt work and I can't edit it for some reason. Here:
The file has the wrong name. It says it should be named "mmcblk0p4" while mine is named "nmdsdcid"...
http://i.imgur.com/ebkcMVo.png
And my last post did save even though it never did...

timmaaa said:
It isn't dangerous if you follow the instructions exactly.
Unlock your bootloader > install TWRP > flash superuser or rooted ROM to get root > hex edit your CID > get s-off > flash whatever you want.
Sent from my Evita
Click to expand...
Click to collapse
I dun goof somewhere. I finally found the file (it appeared out of nowhere), got super CID and then when I tried getting S-OFF from this page http://forum.xda-developers.com/showthread.php?t=2155071 I got error 99 instead of 92. On top of that I got an error on 7-c.
I tried this http://forum.xda-developers.com/showthread.php?t=2155071&page=17
Ok folks thanks to c5satelite and other helpful folks at S OFF PARTY AND IRC we figured out how to fix this whole "error 99" shenanigans.
Step 1. Download the latest stockish ROM (I used Viper 3.2.3)
Step 2. Boot into bootloader and fastboot flash the kernel.. then reboot back into recovery
Step 3. Wipe /system and factory reset in TWRP
Step 4. Install rom in TWRP
Step 5. For *Viper Only* Don't wipe in Aroma, and uncheck reboot at the end.
Step 6. Reboot into bootloader from recovery (Don't boot into the ROM)
Step 7. Follow the instructions in the OP to a T ... read reread.. go get some coffee.. and try again.. hopefully you see Error 92 and not 99
This worked for me with ViperROM on hboot 2.14
Thank you to all the folks involved you guys are rockstars from Mars!
Click to expand...
Click to collapse
Now somewhere in this process, my phone no longer connects to the computer via usb. So I can't even see the sd card through roms or recovery... and now since i wiped system and did a factory reset I can't transfer files.
I tried pushing with adb, but adb says there is no device connected, even though I have it plugged in USB.
Yay for a soft brick!
Is there anything I can do now, or did I just screw myself over right before the finish line?

When you get error 99 you need to force a reboot to the bootloader by holding volume down and power buttons together, then start again (without the adb reboot bootloader command because you're already in bootloader).
Did you factory reset in bootloader? If so you've corrupted your sd card and need to format it by mounting it in TWRP and formatting in Windows.
Sent from my Evita

timmaaa said:
When you get error 99 you need to force a reboot to the bootloader by holding volume down and power buttons together, then start again (without the adb reboot bootloader command because you're already in bootloader).
Did you factory reset in bootloader? If so you've corrupted your sd card and need to format it by mounting it in TWRP and formatting in Windows.
Sent from my Evita
Click to expand...
Click to collapse
Well... my phone has no recognizable USB. I just did a factory reset in Hboot after you mentioned it, now theres the error cause sd doesnt exist.
BUT i can't mount. When I click mount on TWRP, nothing happens. No external storage appears on my computer... I don't know whats going on.