Develop Bugs

[Q] flashing ruu on branded phones

Can I flash the unbranded ruu on a branded 3 UK phone, will I lose recovery and superuser?
Sent from my HTC One X using Tapatalk 2

newcastle9 said:
Can I flash the unbranded ruu on a branded 3 UK phone, will I lose recovery and superuser?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
If you have unlocked via HTCDev the this would have removed your CID in which case yes you should be able to flash the WWE RUU on a branded device.
If you have not unlocked and are still running stock then no it wont work.

Does HTCDev unlock remove CID? Unless it changed to 11111111 you still won't be able to flash an RUU AFAIK

EddyOS said:
Does HTCDev unlock remove CID? Unless it changed to 11111111 you still won't be able to flash an RUU AFAIK
Click to expand...
Click to collapse
It does indeed. It doesn't change it to 1111111 it completely removes it altogether.
I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back (screen flickering problem) and it worked with no issues.

Vodafone Australia
I am Vodafone Australia and unlocked my phone via HTCdev. I am also facing the same problem (screen flickering)and need to send it back. I have re-locked it. As you just said "I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back" can you please explain how did you re-flash the WWE RUU? steps or link?

Deleted

gilbert_ac said:
I am Vodafone Australia and unlocked my phone via HTCdev. I am also facing the same problem (screen flickering)and need to send it back. I have re-locked it. As you just said "I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back" can you please explain how did you re-flash the WWE RUU? steps or link?
Click to expand...
Click to collapse
You need to get the vodafone au ruu. General wwe releases will not work for you. Pretty sure the correct ruu is available in the dev section.
Can't link, posting from phone.
M.
Sent from my HTC One X using xda premium

Stock RUU for 1.28 needed
Hi there
I have effectively killed my HTC one - I unlocked via htcdev and upgraded the recovery - fastboot shows the device id when running the command fastboot devices.
However I am now stuck in a boot loop where the phone only boots to hboot (following a failed boot.img flash) I have downgraded back to stock recovery and re locked but cant find the 1.28 RUU to recover the device (and I did try the RUU for 1.26 but it wouldnt install)
Once I updated te recovery i ran the fastboot boot boot.img command
This failed to progress past the 'htc quietly brilliant' flash screen.
I dont have the rom .zip saved on my internal memory on the phone - I was hoping to be able to push it to the /data/ partition however when I try this sdb returns no connected device.
Wonder if anyone can assist in either
a - returning to stock with a RUU for 1.28
or
b - advise how to flash the files I need onto the phone (it seems that the ROM isnt booting so I assume its from the point I install boot.img and beyond I need so help)
Unfortunately I cant get the phone to boot to copy files to the memory so need to work entirely in fastboot and adb (assuming adb wil recognise the handset)
Many thanks
Gurry

dr9722 said:
It does indeed. It doesn't change it to 1111111 it completely removes it altogether.
I re locked the bootloader the other day and re-flashed the WWE RUU as im sending it back (screen flickering problem) and it worked with no issues.
Click to expand...
Click to collapse
But relocking it puts it back so unless you were on HTC__001 you'd be back on the VODAP001 CID

[Q] How can I change the CID of my S-OFF One X?

My phone is S-OFF and it is SuperCID(11111111), I found out that I won't receive updates if my phone has this CID. I want to change it to a\n unbranded CID where I can receive the JB OTA. I don't know how, though. Also, what CID do you think will receive the earliest JB OTA once it comes out? And if I am going to change my CID to an unbranded one, can I revert it back to SuperCID once I receive the update?

jed27.galvez said:
My phone is S-OFF and it is SuperCID(11111111), I found out that I won't receive updates if my phone has this CID. I want to change it to a\n unbranded CID where I can receive the JB OTA. I don't know how, though. Also, what CID do you think will receive the earliest JB OTA once it comes out? And if I am going to change my CID to an unbranded one, can I revert it back to SuperCID once I receive the update?
Click to expand...
Click to collapse
just run a RUU and that will make you s-on and with the RUU's CID...

That doesn't sound useful, why would you want to lose S-Off?
HTC_001 is probably the most likely to be first, but I'm not sure if the OTA will work. Do you have stock 2.17.401.2 and stock recovery?

BenPope said:
That doesn't sound useful, why would you want to lose S-Off?
HTC_001 is probably the most likely to be first, but I'm not sure if the OTA will work. Do you have stock 2.17.401.2 and stock recovery?
Click to expand...
Click to collapse
yep i agree, i wouldn't ever ever ever flash a RUU only to get official updates! we will get the official update before it will be released worldwide

I am currently on stock 2.17.401.2 after flashing the RUU a month ago. Before that, I was on 1.15.401.1(!). Stock recovery? I don't know what that means, sorry. Anyway, I don't want to lose my S-OFF just so I can receive updates. I know s-off phones can change CID by fastboot blah blah. Something about writing a command, ugh, I'm not really sure.

You wouldn't even need to flash the RUU...
If you're S-Off, you could just use fastboot oem writecid HTC__001 if you really wanted too, which would change your CID to HTC__001 and keep you S-Off, but i'd say staying SuperCID is the best idea, and just flash one of the many JB roms that are out there.

Brownie2k said:
You wouldn't even need to flash the RUU...
If you're S-Off, you could just use fastboot oem writecid HTC__001 if you really wanted too, which would change your CID to HTC__001 and keep you S-Off, but i'd say staying SuperCID is the best idea, and just flash one of the many JB roms that are out there.
Click to expand...
Click to collapse
I get that. But I am still in the process of learning things since this is my first Android phone. Things are still complicated specially because the tuts on inbstalling custom ROMs are all about S-ON HOXs. Anyway, if I change my CID to a normal unbranded one, can I revert it back to SuperCID?

Yes you could.
You'd just do fastboot oem writecid 11111111.
To get updates though, you'd need to have a locked bootloader, stock rom etc... You phone would basically become a Unbranded European One X. Not sure if flashing the update would put you S-On, which means you'd be stuck as a HTC__001.
Basically if you wanted to try Jellybean, you'd just have to flash the required firmware, followed by a custom recovery then flash the rom. You don't need to unlock bootloader because you're S-Off.

Brownie2k said:
Yes you could.
You'd just do fastboot oem writecid 11111111.
To get updates though, you'd need to have a locked bootloader, stock rom etc... You phone would basically become a Unbranded European One X. Not sure if flashing the update would put you S-On, which means you'd be stuck as a HTC__001.
Basically if you wanted to try Jellybean, you'd just have to flash the required firmware, followed by a custom recovery then flash the rom. You don't need to unlock bootloader because you're S-Off.
Click to expand...
Click to collapse
... and as an added bonus you don't need to flash the boot.img of a custom rom before flashing the Rom itself, as we s-on peeps need to. You can just flash the entire custom rom at once from the custom recovery.
I.E. you won't need a computer when you want to try another rom
Sent from my HTC One X using Tapatalk 2

That's my problem! There should be a thread about S-OFF phones and what to do with them. Haha.

jed27.galvez said:
That's my problem! There should be a thread about S-OFF phones and what to do with them. Haha.
Click to expand...
Click to collapse
Well to be fair, it's very rare to find an S-Off One X at the moment, so count yourself very very lucky!
You hold one big big big advantage over us all though, you can downgrade your HBOOT back to 1.12 if you didn't like Jellybean. Currently for the most of us, with compatible CID's, once we're on HBOOT 1.28, thats it, there is no way back which means things like CM10 etc doesn't work for us.

Actually, you can use CM10 with hboot 1.28, but you have to use the special boot.img posted in the CM10 thread. It works for hboot 1.23 and hboot 1.28.
http://forum.xda-developers.com/showpost.php?p=32486421&postcount=7308

[Q] Relock to send back to Verizon

Hello, just a quick question. I had my One rooted, s-off, and unlocked when my microphone went. So I relocked, s-on, and flashed an RUU via http://forum.xda-developers.com/showthread.php?t=2475216. Just making sure that before I pack it in the box, there is nothing else that could trip the people at Verizon that I had messed with my phone. I took the OTAs up to 4.3. I'm just paranoid about info not matching up such as the baseband version and build number etc. Thanks

Does the bootloader say locked or relocked? Locked is good relocked not so much. Other than that you should be fine. Ruu's wipe everything and install it all fresh, including the firmware (baseband, hboot, recovery, etc), so everything will match up.

In the bootloader I have "Locked" also s-on. I noticed though with the refurbished phone I received (not happy about having to get refurbished but thats besides the point) the CID number shows in the bootloader screen whereas on my original phone it is not displayed. Not sure if I even need to be this worried, but I'm just paranoid. Thanks

Are both phones on the same hboot version? I dont remember if it showed in older hboots or not. Either way i wouldn't worry, locked and s-on is all you need.

No they weren't. I'm just going to stop worrying too much about it. Thanks

If i send my phone back to verizon do i have to be on the original ROM? i understand that i need to lock my bootloader and have s-on, but what about the software itself?

It can be on stock rom/firmware of any version. Just no custom roms or anything.

Just to confirm, if I have a phone that is S-OFF, unlocked:
1. Do I need to lock the bootloader before flashing an RUU?
2. Does flashing an RUU revert the phone to S-ON?
3. Does anything special otherwise need to be done to the phone prior to flashing the RUU?
Thanks so much in advance.
I also have to return a phone to VZW due to a hardware issue (the autofocus issue finally too much for me to bear).

You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.

Fantastically clear, Clumsco, thanks! Three quick additional questions
1. is there any advantage to flashing the signed RUU, and adding danger by locking the bootloader beforehand? In your links below your signature is a path to both decrypted and signed versions of the latest RUUs. So I thought to ask before going with one or the other. If there is no advantage then I guess the decrypted version would be the safer bet, right?
2. Is there a danger that locking after the RUU will result in a "relocked" versus the desired "Locked" status?
3. Will the RUU flash wipe my /sdcard area? If so I'll back everything up before embarking on this.
I VERY much appreciate the help. I ran rumrunner several months back and have forgotten a lot of the nuances. Thanks for the quick primer!
cmlusco said:
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Click to expand...
Click to collapse

There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.

Thanks, everything worked. For future knowledge, can you flash signed RUU's with an S-ON device?
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse

Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.

cmlusco said:
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
Click to expand...
Click to collapse
I'm trying to learn here too, that is dependent on the hboot correct? So if you were to downgrade your hboot via the thread somewhere in the VZW HTC One forum, you should be able to flash any RUU right?

Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.

Your responses are clear and helpful. Thanks a bunch!
cmlusco said:
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Click to expand...
Click to collapse

cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
My phone is current S-Off and relocked, how can I change it to unlocked?
Thank you.
UPDATE: Nevermind, I got it here: http://forum.xda-developers.com/showthread.php?t=2470340

[SOLVED]How to get official updates after relocking bootloader?

Hello to everyone!
I have HTC M8(second hand...) I check the IMEI and i see is from Australia - Sold to Singapore. I don't know if it means something.
It was unlocked bootloader and modified software(Custom ROM-android 6), S-OFF and CID was 11111111(I don't know what was the original CID, because this is how i bought the phone)
I decided to get it back to stock. I found a few threads about how to get the HTC M8 fully stock, but nothing works for now. l have the the stock recovery, stock boot.img and locked the bootloader.
When i installed/restored from the RUU file it was ok. When i check for updates it's downloading, but cannot install.
There is a message:
'Variant system version - We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system please contact us via the support section at HTC - Mobile Phones, Smartphones, Cell Phones, Tablets'
I'm sure i have official software, stock recovery and boot.img, but i have no idea why this message appears.
Right now i am using InsertCoin ROM and i have noticed the message, that tells "Software status: Modified or Official" Mine tells always OFFICIAL. No matter if i have installed insertcoin or stock rom.
Here is the infor from my bootloader:
***Software status: Official*** (Just to remind... I'm with insertcoin rom)
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.16.401.10
eMMC-boot 2048MB
Jan 15 2015, 22:51:08.0
Can anyone tell me how to download the official updates?
(sorry for my english)

No one can help with this ?

Jared89 said:
I decided to get it back to stock. I found a few threads about how to get the HTC M8 fully stock, but nothing works for now. l have the the stock recovery, stock boot.img and locked the bootloader.
Click to expand...
Click to collapse
None of that includes an actual stock ROM, which is required to OTA.
Jared89 said:
When i installed/restored from the RUU file it was ok. When i check for updates it's downloading, but cannot install.
Click to expand...
Click to collapse
You're sure the RUU installed correctly, with no errors?
Did you try to update immediately after RUU, with not mods at all (unlocking the bootloader, root, custom ROM)?

redpoint73 said:
None of that includes an actual stock ROM, which is required to OTA.
You're sure the RUU installed correctly, with no errors?
Did you try to update immediately after RUU, with not mods at all (unlocking the bootloader, root, custom ROM)?
Click to expand...
Click to collapse
Yes. I have no errors during the installing process and after that...
And yes... I try to update immediately after the phone boot to the home screen. I have no idea how to fix this. With my previous HTC M8 i was using the same custom rom(InsertCoin) and when i decidet to go back to stock, all i was doing is to lock the bootloader and install the RUU. Then i'm able to get the updates with no problems.

Jared89 said:
when i decidet to go back to stock, all i was doing is to lock the bootloader and install the RUU. Then i'm able to get the updates with no problems.
Click to expand...
Click to collapse
Yes, its strange. RUU by definition should put you on a fully stock image, and therefore allow OTA updates.
You can try to RUU straight to 6.12.401: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Curious to see if you get the same error with that RUU.

redpoint73 said:
Yes, its strange. RUU by definition should put you on a fully stock image, and therefore allow OTA updates.
You can try to RUU straight to 6.12.401: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Curious to see if you get the same error with that RUU.
Click to expand...
Click to collapse
I was trying this a few times. It says there is not enough space or something. C

I'm still looking for solution. Any suggestion is welcome!

Are you still S-OFF? On the M9 one hast to change the CID from SuperCID (11111111) back to a WWE CID to take the update to MM, as HTC uses a new routine to check the state of the phone.
In your case you'd have to reboot to fastboot mode, open a command prompt and change the CID to HTC__001 (8 digits!!) by using the command "fastboot oem writecid HTC__001"
Send by the swarm intelligence of my coffee machine ?.

Yes, i'm still S-OFF.
Thanks! I will try it and i will let you know if it works.

HTCNerdYoda said:
Are you still S-OFF? On the M9 one hast to change the CID from SuperCID (11111111) back to a WWE CID to take the update to MM, as HTC uses a new routine to check the state of the phone.
In your case you'd have to reboot to fastboot mode, open a command prompt and change the CID to HTC__001 (8 digits!!) by using the command "fastboot oem writecid HTC__001"
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
I just try your method, but when i try to get it back to stock with RUU.exe i get Error 130, which means is a wrong device. I gues i will have to get back the super CID?

Jared89 said:
I just try your method, but when i try to get it back to stock with RUU.exe i get Error 130, which means is a wrong device. I gues i will have to get back the super CID?
Click to expand...
Click to collapse
Which RUU are you using? In case of an x.xx.401.x RUU it is indeed WWE. Thus the CID should be HTC__001 or HTC__102.
maybe you should tray to RUU with the later one and if it doesn't work go back to SuperCID.
Send by the swarm intelligence of my coffee machine ?.

HTCNerdYoda said:
Which RUU are you using? In case of an x.xx.401.x RUU it is indeed WWE. Thus the CID should be HTC__001 or HTC__102.
maybe you should tray to RUU with the later one and if it doesn't work go back to SuperCID.
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
4.16.401.10 Europe.
I can't use the latest RUU, because is only on ZIP file. When i try to install it with fastboot it says there is no space or something.

You could rename the RUU zip to 0P6BIMG.zip and copy it to the root direction of a - at max - 32GB microSD card that has been formatted to fat32.
Insert this SD into your M8 and reboot to bootloader. It will then recognize the RUU and start to flash it automatically.
After a full flash you got to take the SD Card out again, to prevent it to start again during the next reboot
Send by the swarm intelligence of my coffee machine ?.

HTCNerdYoda said:
You could rename the RUU zip to 0P6BIMG.zip and copy it to the root direction of a - at max - 32GB microSD card that has been formatted to fat32.
Insert this SD into your M8 and reboot to bootloader. It will then recognize the RUU and start to flash it automatically.
After a full flash you got to take the SD Card out again, to prevent it to start again during the next reboot
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
I'll try this later. Just flashed the RUU(4.16.401.10_Europe), but even with CID HTC__02 i get "Variant system version" message...

Jared89 said:
I'll try this later. Just flashed the RUU(4.16.401.10_Europe), but even with CID HTC__02 i get "Variant system version" message...
Click to expand...
Click to collapse
Sure you took HTC__02, as it hast to have 8 digits and thus HTC__102. In case it doesn't help return to SuperCID 11111111.
Send by the swarm intelligence of my coffee machine ?.

HTCNerdYoda said:
Sure you took HTC__02, as it hast to have 8 digits and thus HTC__102. In case it doesn't help return to SuperCID 11111111.
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
Nothing works for now. I bring it back to InsertCoin rom.
My phone is from Singapore, so i might need the correct RUU for it. I have no idea!

Jared89 said:
Nothing works for now. I bring it back to InsertCoin rom.
My phone is from Singapore, so i might need the correct RUU for it. I have no idea!
Click to expand...
Click to collapse
Your problem is not the SuperCID 11111111 but wrong MID for the ROM that you installed.
To run a EU RUU x.xx.401.x, the MID must be 0P6B10000
You said your device is from Singapore, most probably the MID is 0P6B11000 and that's the reason for your "Variant System Version" error.
You can check your current MID by running command fastboot getvar mid
And for S-Off, there is no need to relock bootloader for OTA or running a RUU.

ckpv5 said:
Your problem is not the SuperCID 11111111 but wrong MID for the ROM that you installed.
To run a EU RUU x.xx.401.x, the MID must be 0P6B10000
You said your device is from Singapore, most probably the MID is 0P6B11000 and that's the reason for your "Variant System Version" error.
You can check your current MID by running command fastboot getvar mid
And for S-Off, there is no need to relock bootloader for OTA or running a RUU.
Click to expand...
Click to collapse
Didn't think about that. MID is 0P6B11000, as you said. I have changed it to 0P6B10000. I'll try later if i get the updates. Thanks a lot for the info!

Ok, when i changed MID the problem was solved! Now i get all the updates! Thanks a lot!
I followed instructions from this post:
http://forum.xda-developers.com/showthread.php?t=2708581

Unrooting T-Mobile M8 Questions

Hey guys, I know there's a crazy amount of unrooting threads here and everywhere else on the internet, but the more I search the more confused I get. So here's my short situation and my few questions:
Got a T-mobile M8, rooted, S-On, Unlocked, Running S.ROM. I'm trying to do the Tmobile JUMP thing to get the new HTC 10, so I'm trying to unroot this as much as possible. I've found at least 7 different ways with different outcomes on how to do this, so here are my questions:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
-Follow up to previous question: has anyone had any experience with returning a Relocked phone to Tmobile for their JUMP plan? (Not warranty exchange, I feel they're more strict with that)
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Thanks in advance!

TehAsher said:
-I keep reading you can just flash the RUU with no other prerequisites and it'll take your phone back to stock (except for the "Relocked" status). Is this true?
Click to expand...
Click to collapse
The statement "no other prerequisites" is not specific enough. If you mean stock ROM and/or stock recovery (which folks sometimes think is needed to RUU), its true that neither are needed in order to RUU.
There are however some prerequisites:
1) PC required. Win7 and USB 2.0 for the best compatibility with RUU.
2) RUU needs to be intended for your version (CID and MID)
3) RUU version needs to be greater or equal to main version on the phone (this requirement is bypassed with s-off)
4) Relocked or locked bootloaded (this requirement also bypassed with s-off)
TehAsher said:
-Is the only way to change the Relocked status to Locked by going S-Off with Sunshine and doing all of the 8923479324 steps in order to erase all of the tampered flags?
Click to expand...
Click to collapse
Correct.
TehAsher said:
-What is the BEST method with the BEST outcome to go back to full stock on the M8?
Click to expand...
Click to collapse
T-Mob is not my carrier, and I know nothing of their Jump program. But in most cases, the best bet with returning a phone is to RUU to stock, and make the bootloader LOCKED. Return to s-on (after s-off) is probably not needed.

Thanks for the info! I guess I'll be getting sunshine then and try to follow all of these guides. So if I S-off with sunshine, as long as I check my CID and MID (I got the RUU from the HTC website, but I'll double check it anyways), I can flash that and return to stock. And afterwards I can find a guide on how to reset the tampered flags and the Locked status?

TehAsher said:
And afterwards I can find a guide on how to reset the tampered flags and the Locked status?
Click to expand...
Click to collapse
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571

How I went back to stock
I was rooted and running custom ROMS, but when MM came out I wanted to make sure that my firmware/radio was updated. So for me this is what I did
- first I am s-on
- When I unlocked the bootloader, just before I installed TWRP, I made a copy of the recovery. Also I backed up my stock ROM. Both I kept
So to restore:
- I re-installed via TWRP, the stock ROM, and made sure that I didn't root it
- I re-installed the stock recovery
- rebooted and phone saw the MM upgrade and proceeded to upgrade.
If you don't have the recovery/stock ROM you will need to remember what version of android you were on when you overwrote the recovery with TWRP. If your firmware + recovery + OS do not match the update won't work.
-brad

redpoint73 said:
Yes, that is what I would suggest. Guide on how to make it LOCKED and remove TAMPERED:
http://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Awesome, got my phone S-Off. I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?

TehAsher said:
I tried installing the RUU from the HTC website but I got an error and it failed, saying something about I'm using the wrong RUU. This is my CID and MID:
MID: 0P6B13000
CID: T-MOB010
I used this link to get my RUU:
http://www.htc.com/us/support/rom-downloads.html#tmobile
Am I doing something wrong?
Click to expand...
Click to collapse
What error number? If 155 or 159, you can't RUU from LP to MM (this is a new requirement they added with MM). You either need to flash the 6.20.531.5 full stock firmware from here, then run the RUU again. Or run the T-Mobile LP RUU.