Database Info

How can I get back to the stock rom in AT&T HTC One X

Hello every one,
since HOX from AT&T was sim locked I thought maybe one of the customroms have the ability to unlock the sim but non of them does that.
So now I want to go back to the original "Stock rom" that the HOX from AT&T came with if that possible and how?
I would really appreciate the help.
thanks a lot in advance.

Well unlocking sim has nothing to do with any rom whatsoever.
There are several threads already covering this topic of going back to stock with an RUU
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Well unlocking sim has nothing to do with any rom whatsoever.
There are several threads already covering this topic of going back to stock with an RUU
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks, but can you guide me to one of these threads related the the HOX, because I was looking for one but I seem not to find them, Sorry

shakash3obd said:
Thanks, but can you guide me to one of these threads related the the HOX, because I was looking for one but I seem not to find them, Sorry
Click to expand...
Click to collapse
Download RUU
Plug phone in
Relock bootloader
Run RUU.exe
That's pretty much it. Its not rocket science.
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Download RUU
Plug phone in
Relock bootloader
Run RUU.exe
That's pretty much it. Its not rocket science.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I know it's not rocket science, but even before I created this thread, I knew that I need to do what you just said but my problems were the following:
When I was trying to relock the bootloader using the windows command line, I got the following message
< waiting for device >
and that stayed there forever, I mean I was waiting for 2 hours just to make sure wither something working or not but it wasn't doing anything.
I got the previous message when I typed the following command
fastboot oem lock
-------
I thought maybe I need to run the RUU first, then I should relock the bootloader but even doing that ended up with error.
By the way, the RUU I used is
RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed
and I am currently downloading
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
and I will see if this one works or not.
I hope you can see that I didn't post this thread without doing some search first but in fact it was the time to ask for help so it is not laziness.
Thanks

waiting for device indicates it doesnt see your phone. are you in fastboot USB when you run the command?
do you have FAST BOOT disabled in the OS (settings, power)
there are a couple of tutorials already available on this exact subject...not sure what it is you are looking for at this point, but it sounds like you need to get your computer to see the device
there is zero need to wait 2 hours for fastboot to show up on computer, it should happen immediately assuming you are actually in FASTBOOT USB mode
remember UNLOCKING the phone with HTCDEV?
you pretty much follow those guidelines to get
fastboot oem lock
to work
then you can run the RUU, any RUU made for your device (CINGULAR RUU is correct)

Can't flash a ROM. Help!

I can get it to get into recovery mode, but it wont go any further than the red lettered warning banner. I tried to flash the ROM from the clockwork mod app from the market. No luck. My phone is not in the list of phones in the "Flash clockwork mod recovery". I tried to flash the 5.8.4.0 endeavoru.img file to my phone, but in my command prompt on my computer, it doesn't recognize my command as a batch command or anything. Any help folks? I was trying to find a stick on rooting, unlocking bootloader, and then flasing roms, but to my surprise I didn't find them all in one. I don't know what I'm doing wrong at this point. Spent a few hours last night, and now it all seems like a blur. Help please!

CP24EVA said:
I can get it to get into recovery mode, but it wont go any further than the red lettered warning banner. I tried to flash the ROM from the clockwork mod app from the market. No luck. My phone is not in the list of phones in the "Flash clockwork mod recovery". I tried to flash the 5.8.4.0 endeavoru.img file to my phone, but in my command prompt on my computer, it doesn't recognize my command as a batch command or anything. Any help folks? I was trying to find a stick on rooting, unlocking bootloader, and then flasing roms, but to my surprise I didn't find them all in one. I don't know what I'm doing wrong at this point. Spent a few hours last night, and now it all seems like a blur. Help please!
Click to expand...
Click to collapse
Do some research first because seems like u don't have even a custom recovery or even roooted... Now also never install anything that says endeavour or you will **** up your phone enough said...now do u have att one x or rogers telstra

WOAH, STOP RIGHT THERE.
endeavoru.img IS THE WRONG IMAGE!!!! I can smell a brick!!! the endeavoru image is for the quad core tegra one x. I am assuming you have a OneXL or one of the other Qualcomm DUAL CORE One X's
Our phone is called EVITA.
If you have a non ATT one x like a Telstra One XL or rodgers go to htcdev website.
If you have a ATT version I have recently found out that some versions cannot be rooted, and root is needed to unlock the bootloader. If it has ATT logo on the top where HTC should be, then you need to know the version number of your current rom before putting in any more effort to unlock. Check settings>about phone>
Check the forum in the One X Android Development/[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 10/2/12) for the versions that can be rooted/unlocked.
Hope this helps
-Liam

mine is the ATT version......
My phone isn't bricked yet...phew. SO....going to get the EVITA then. right? for ATT version?

First thing is first you need to know the version of the stock rom you have, go to settings/about phone, I believe that if your version is greater than 1.85 then you are pretty screwed. You can only wait until A) ATT allow unlocking B) someone finds an exploit. If your One X is brand new, I doubt it is 1.85 as this is an old version.

llambkin said:
First thing is first you need to know the version of the stock rom you have, go to settings/about phone, I believe that if your version is greater than 1.85 then you are pretty screwed. You can only wait until A) ATT allow unlocking B) someone finds an exploit. If your One X is brand new, I doubt it is 1.85 as this is an old version.
Click to expand...
Click to collapse
Many phones are still being sent out with 1.85/1.73:angel: and to op DONT use clock word mod oonce you root and unlock bootloader I will show u which recovery to flash

WOW, Thats good. Ours are shipped with the latest, well at least my sisters one was. I thought she would have been screwed, But I was able to unlock with HTCDEV
@omario8484, is there a reason for not using CWM? I have it on my OneXL. I got the touch version, TWRP is good I guess, but I am more familiar with the CWM interface.
-Liam

omario8484 said:
Many phones are still being sent out with 1.85/1.73:angel: and to op DONT use clock word mod oonce you root and unlock bootloader I will show u which recovery to flash
Click to expand...
Click to collapse
I'm simply looking for a link to the evita version. I keep seeing the other one .
Sent from my HTC One X using Tapatalk 2

Also mine was 1.82. Found it on craigslist.
Sent from my HTC One X using Tapatalk 2

AWESOME!!!
Try This http://forum.xda-developers.com/showthread.php?t=1777773
:good:

CP24EVA said:
Also mine was 1.82. Found it on craigslist.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
That's because clock work doesn't support out phone officially !!!!!!!!!!!!!

ChummyDays said:
If you flash some roms with cwm, they sometimes will have serious problems. Twrp works with very Rom perfectly fine.
Click to expand...
Click to collapse
OK, I might flash back to TWRP then, I have always used CWM....I did like the skinnable interface of TWRP tho :

llambkin said:
OK, I might flash back to TWRP then, I have always used CWM....I did like the skinnable interface of TWRP tho :
Click to expand...
Click to collapse
Yes use twrp because USB mount works also some Tom's like he said will have problems

Ok, I got it all sorted. Out. My main problem is I didn't know what the goo interface let me do. Once I found out then it was cake from there. I'm loving this AOKP one so far.

I there a way to get to the play store that doesn't include using an internet browser?

CP24EVA said:
I there a way to get to the play store that doesn't include using an internet browser?
Click to expand...
Click to collapse
Maybe the play store app?

I don't see a play store app in the app tray at all. and when I press the PLAY STORE option in the menu tray, it does nothing.

[Q] No backlight

I've been running ViperXL (Bulletprrof 1.3 kernel) just fine fine for a few weeks. It's been nearly flawless. Just now, though, the backlight went out and nothing I do seems to bring it back on. I've rebooted, plugged into AC, and tried booting into recovery. In the sunlight I can see just enough to know the device is on. I've managed to get into settings, which thankfully has a white background, and verified that brightness is at max.
There is no backlight even through the reboot process.

ctennenh said:
I've been running ViperXL (Bulletprrof 1.3 kernel) just fine fine for a few weeks. It's been nearly flawless. Just now, though, the backlight went out and nothing I do seems to bring it back on. I've rebooted, plugged into AC, and tried booting into recovery. In the sunlight I can see just enough to know the device is on. I've managed to get into settings, which thankfully has a white background, and verified that brightness is at max.
There is no backlight even through the reboot process.
Click to expand...
Click to collapse
When you reboot the phone, does the boot image (Default HTC Screen) also have no backlight? Or in recovery is there a backlight? If not, it's a hardware failure. Screen would need to be replaced. If the backlight comes on when in recovery or during first boot image, then it's something software related which is easier to fix.

There's no backlight anywhere. I know it's not kernel since I was able to fastboot flash the default kernel for ViperXL over USB.
If I bought this through AT&T less than a year ago does anyone know if it's under warranty? I'd hate to pay to get the screen replaced. I'd rather try to get it back to stock and take it in.
That's assuming, of course, someone can point me to instructions for getting back to stock! I've looked but haven't seen any in the forum.

It's hardware. You need a new screen. You would need to s-off if you're not already and then run the appropriate ruu for your carrier. I believe at&t will warrant it np.
S-off directions are stickied in original android dev section and ruu's can be found in the resource compilation thread linked in my signature.
Make sure to download an executable Ile and not a zip. Easier to return to stock with exe
Sent from my HTC One X using xda app-developers app

exad said:
It's hardware. You need a new screen. You would need to s-off if you're not already and then run the appropriate ruu for your carrier. I believe at&t will warrant it np.
S-off directions are stickied in original android dev section and ruu's can be found in the resource compilation thread linked in my signature.
Make sure to download an executable Ile and not a zip. Easier to return to stock with exe
Click to expand...
Click to collapse
Thanks a ton. I'm already S-Off. I spoke with customer service and they're going to send me a replacement device (same model, though I asked if it was possible to change). Should I be using the one labeled [ruu] [stock] att 2.20 ota? There are a few whose names look like what I might want.

No you'll want one that is ruu and not ota. Doesn't matter what version so long as it's at&t. The filename will end with exe
Sent from my HTC One X using xda app-developers app

exad said:
No you'll want one that is ruu and not ota. Doesn't matter what version so long as it's at&t. The filename will end with exe
Click to expand...
Click to collapse
Ok, so like [STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502 ? And the RUU will wipe anything that's not stock, right? Thanks.

It will return your phone to stock but your bootloader will still be unlocked and you will still have s-off. You can spoof it like it's never been unlocked and return it to s-on though I doubt that would be worth the trouble.
Sent from my HTC One X using xda app-developers app

exad said:
It will return your phone to stock but your bootloader will still be unlocked and you will still have s-off. You can spoof it like it's never been unlocked and return it to s-on though I doubt that would be worth the trouble.
Click to expand...
Click to collapse
I see. So you don't think they'd bother digging too deeply to notice it's s-off and unlocked? I'll run the RUU tonight and check in later.
I really appreciate your help this evening.

Since it's a hardware issue, I doubt they'll care to dig That far into it. From what I see on here AT&T is pretty lenient about unlocked phones, especially when it's a hardware issue.
Sent from my Sony Tablet S using xda app-developers app

I'm having difficulty running the RUU. I've rebooted and connected my device to my computer and run the RUU utility. It says it can't find the device and to check the connection. I can't see the screen well enough to turn debug mode on or off on the device. What can I do to run the RUU?

Try running while in bootloader/fastboot?
Sent from my Sony Tablet S using xda app-developers app

That did it, thanks. Now to wait until the sun is bright enough out today to wipe the SD card through settings.
I'm going to miss being rooted.

(Solved)Stuck in Bootloader/Relocked

I am currently stuck in the bootloader. To make matters worse, I relocked to RUU and am stuck at Sending with that. I am Super CID which I think is the problem. To make matters even worse, I no longer have my unlock_code.bin file.
Is there any hope for my phone? Also, the RUU process has completely wiped my phone. Thanks for any input in advance. I have searched and searched for an answer but haven't found anything useful.
Sent from my HTC One XL using XDA Premium 4 mobile app

You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita

timmaaa said:
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
Click to expand...
Click to collapse
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app

//JavaJ said:
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Sent from my Evita

timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse

//JavaJ said:
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have a locked bootloader and the correct CID there should be no harm in running the RUU. The unlock process (from memory, I could be wrong) doesn't require the phone to be booted into an os, it's all taken care of while the phone is in bootloader. That's kinda irrelevant now anyway as it isn't possible anymore.
Are you using the usb cable that came with the phone? You can try using a different usb port, usually the ones on the back of the pc tower are the best.
May I ask, how exactly do you think the s-off process screwed up the phone? It either succeeds or fails, and there should be no serious repercussions from either.
Sent from my Evita
Click to expand...
Click to collapse

Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app

//JavaJ said:
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita

timmaaa said:
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
Click to expand...
Click to collapse
Took your advice about the usb port. Switched it to the back and the ruu worked. Will I be able to run the root exploit again? Yes, this definitely has been a learning experience. Coupled with my lack of sleep and overall frustration I made some bad moves. Thanks for your patience and help though. Much appreciated.
And no, I could not get back into recovery after I relocked it. It would send me right back to the bootloader. Also, I did do a factory reset from the bootloader. Believe me, taking mental notes all the way here.
Sent from my HTC One XL using XDA Premium 4 mobile app

Now that you have a working os, you could be able to use the exploit again to unlock the bootloader etc. Just take it slowly though, do some reading so you gain a bit of knowledge. And if you have any questions, don't be afraid to ask.
Sent from my Evita

Unlocked and rooted. Again. Thanks for your help. Leary of trying to s off again though
Sent from my HTC One XL using XDA Premium 4 mobile app

Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita

timmaaa said:
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
Click to expand...
Click to collapse
Yes, I have done it before, on my One X. Not quite sure what went wrong. Maybe the issue with my wife's phone was preexisting and reared it's ugly head in the process. I have been rooting and nodding phones for years. I am not a complete noob. I am experienced in java programming and have created many interesting applications for my phone. Perhaps I should take my java knowledge and automate my s off experience.
Sent from my HTC One XL using XDA Premium 4 mobile app

If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita

timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Very nice found Tim.....:thumbup:
Swyped From BlueICESense_JBE

timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app

//JavaJ said:
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita

timmaaa said:
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
Click to expand...
Click to collapse
Just wanted to let you know that I went through s off and all went well. Only thing I can think was the problem was that either there was a pre existing corruption on the phone, or the usb port I was using.
Sent from my HTC One XL using XDA Premium 4 mobile app

It could have been anything. It's becoming more and more apparent that different things halt the process for different users. It makes it really difficult to troubleshoot when helping someone through the process. In the end you got it though which is great.
Sent from my Evita

why you should NOT turn s-on!

i got this pm and i thot it was worth everyone to see. while i do not recomend turning any device s on,a verizon device that is not unlockable via htcdev is of much more importance,as the only thing that can rescue it is a new enough,signed RUU.
it really is not worth the risk,i promise.
nicholi2789 said:
scotty1223 said:
nicholi2789 said:
Hey there, Sorry to bother you with a PM like a noob, but I just have a quick question for you. I have just received a Certified like new replacement M8 from Verizon because my original one had a manufacturer defect. My original one was S-OFF, rooted, with custom recovery and the latest firmware (1.55.605.2) from Verizon. I'm trying to get it back to as close to stock as possible so Verizon doesn't try and say I modified it and mak me pay for it. I already un-rooted it, flashed stock recovery, and took the latest OTA so my radios match my software version. Then I followed this thread: http://forum.xda-developers.com/showthread.php?t=2708571
to re-lock the bootloader and set the lock status flag. It says locked again in fastboot.
The only thing I have left is the S-OFF that displays in fastboot. I'm trying to find a way to reset that, or at least modify it so it shows S-ON. That way if by some weird chance a Verizon employee boots it to fastboot it will show completely stock and S-ON.
Now i've found this thread: http://forum.xda-developers.com/showthread.php?t=2475216 for resetting the S-OFF flag. I posted in it and asked if it would work on the M8 and nobody could give me an answer. XDA member brymaster5000 told me to ask you and that you could provide an answer.
So finally, my question is, will this fastboot command "fastboot oem writesecureflag 3" work to set my M8 back to S-ON? I know it works on the M7 but nobody can tell me for sure on the M8.
Thanks alot for your time.
Nick
Click to expand...
Click to collapse
I would very strongly recommend that you do not turn s on. Phones came s off ,so leaving out that way is not an issue.
Turning s on may open a can of worms that you cannot recover from,and then you're paying for a phone for sure.
As long as your stock rom, recovery and locked you're good to go
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
What do you mean phones came s-off? Verizon sent people m8s that already were s-off? It just seems like a super obvious indication that the device was modified. Your not the first person that has said that going back to s-on is a bad idea, so I will listen and not tempt fate. But iam curious, What can happen by doing that command that could cause such problems? And don't stock RUUs return you to s-on? Or do they just reset everything else but s-off?
Click to expand...
Click to collapse
before any phone is released,batches are sent off to testers and these devices are always s off. i have owned several factory s off devices,and there is no way of proving the phone you have did not come this way. further, large phone resellers are able to use factory htc diagnostic files to clear security data(sim lock,s off,cid/mid),wich again is a legitimate reason a phone is s off.finding s off in the bootloader is not by any means a "super obvious" indication of having been messed with.
turning the phone s on could cause the tampered flag to reset(we dont completely understand all the things that trip it) or you could end up locked into bootloader with a security warning if the boot,system or recovery are not stock enough. either of these things ARE super obvious indicators that you have messed with it,and tried to hide it.
in the case of the security warning,the only course of action is to:
1)run a signed ruu(wich must meet many criteria since youre now s on)
or
2)re-unlock the bootloader. as you know,using htcdev to unlock is not possible with vzw
an ruu does not change/update the partition where the secutity flag lives and thus will NOT turn you s on.

Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk

wtoj34 said:
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.

thunderbls said:
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
Click to expand...
Click to collapse
You have missed the point... If you are locked into the bootloader with a security warning and s-on, you can not use weak sauce and firewater
Sent from my HTC One VX using Tapatalk

People need to realize that verizon reps and techs see hundreds of phones, they don't know the details of every device. The security and bootloader status is obvious to us because it's our device and we know everything about it. To a samsung person they won't know WTF your talking about.
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?

l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk

scotty1223 said:
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
Yes, I misinterpreted the comment as general ease of use which makes me look like an idiot given the reason for the response.... my apologies and note to self read xda after nap lol.

l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.

scotty1223 said:
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
Click to expand...
Click to collapse
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.

l7777 said:
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
Click to expand...
Click to collapse
I agree completely.
Sent from my HTC One using Tapatalk

scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk

dottat said:
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2

How do you reset tampered?
scotty1223 said:
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse

Paulb787 said:
How do you reset tampered?
Click to expand...
Click to collapse
Search this forum for a thread. I'm at work, I can't link it at the moment
Sent from my HTC One VX using Tapatalk

scotty1223 said:
So far, no m8 ruus yet. Hopefully some start popping up.
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk

Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.

nicholi2789 said:
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
Click to expand...
Click to collapse
I didn't mean to embarrass you. They were good questions I thot everyone should read. I should have asked you,and can edit them if you wish.
Sent from my HTC PG09410 using Tapatalk 2

scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nah I wasn't really embarrassed. Haha. I just meant that it's slightly embarrassing that I knew so little about HTC devices, but not a big deal or anything. You were right to post it though, there is some good information there that will do lots of people good.

dottat said:
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Definately a great rescue resource. I just want to make sure that folks understand that since it is unsigned,it will do them no good if they are s on,and stuck in bootloader with a security warning.
As you said,they must stay s off to benefit.(further supporting the point of this thread- don't turn s on)
Sent from my HTC PG09410 using Tapatalk 2

I was going to relock/S-On my defective M8 before returning it. I didn't have time though, and ended up just sending back only wiped and un-rooted, although I don't think /system was 100% stock. VZW sent me a text:
VZW FREE MSG: Thank You! The defective device you recently returned has been received by Verizon Wireless.
Click to expand...
Click to collapse
That was several weeks ago, haven't heard a thing since. I'm assuming they didn't care it was unlocked, or they are very slow at processing the devices.