Database Info

Bought my One X with a ROM and rooted, how to get back to stock?

I'm not sure how to get back to stock as I purchased my phone off craigslist and it has CM10 on it with a custom recovery (TWRP or something I believe). I would like to get back to completely stock as if I purchased the phone brand new from AT&T. I searched through the forums and found stock RUU's but I'm not sure which one to use or how to flash it.
I would appreciate any help at all. Thank you.

Give it time and your question will be answer in here
Sent from my HTC One X using xda premium
---------- Post added at 07:46 PM ---------- Previous post was at 07:41 PM ----------
Also this need to be posted in the question section to be answer.
Sent from my HTC One X using xda premium

Check your hboot version ...if 1.14 relock bootloader then run the 2.20 ruu...if your on 1.09 or 1.11 I guess if you wanna go back to stock and have no desire of rooting then just relock and run the 2.20 ruu

Not really sure why you would want to be back at bone stock seeing as the warranty is gone with no chance to reverse it. Even if you get the boot loader relocked it states Relocked on the bootloader screen. Just flash a stock rom... and keep super user so you can remove all AT&T's bloat. The phones memory is already small as it is, no reason to waste it on crap apps.

Mrkrackie said:
Not really sure why you would want to be back at bone stock seeing as the warranty is gone with no chance to reverse it. Even if you get the boot loader relocked it states Relocked on the bootloader screen. Just flash a stock rom... and keep super user so you can remove all AT&T's bloat. The phones memory is already small as it is, no reason to waste it on crap apps.
Click to expand...
Click to collapse
Selling it, buying nexus 4

brian85 said:
Selling it, buying nexus 4
Click to expand...
Click to collapse
Ah I gotcha, well seeing how you can't ever return to true stock (the day you first got it) I'd just flash a stock ROM and call it a day. Trying to relock the boot loader is a waste of time. Since it will make no difference.
Sent from my One X using xda app-developers app

Mrkrackie said:
Ah I gotcha, well seeing how you can't ever return to true stock (the day you first got it) I'd just flash a stock ROM and call it a day. Trying to relock the boot loader is a waste of time. Since it will make no difference.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sure you can. Just change the cid hex in mmcblk0p4
Only difference is bootloader will say relocked and not locked
Sent from my One X using xda app-developers app

i wouldnt change cid back. id just ruu then give the guy your selling it to the unlock token incase the buyer wants to mod it. save the person some time. if you want to just run the 1.85 ruu you can still get it from htc http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe

absolutelygrim said:
Sure you can. Just change the cid hex in mmcblk0p4
Only difference is bootloader will say relocked and not locked
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Which is still not true stock. You cannot get the boot loader back to factory locked. The warranty is gone and cannot be recovered so these steps that are being taken are useless and make extra hurdles for the buyer if they plan to root. I'd recommend just selling it with a stock ROM on it with the boot loader left unlocked.
Sent from my HTC One XL using xda app-developers app

Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
Nice Grammar, wrong section all together.
http://forum.xda-developers.com/forumdisplay.php?f=1013

Is stock recovery required before flashing a RUU?

no, all you need to do is get into bootloader and "fastboot oem lock" then flash ruu.

mbh87 said:
Is stock recovery required before flashing a RUU?
Click to expand...
Click to collapse
i suppose you have twrp recovery right?
if you have, then just flash device with cleanrom. or stock.
i personally prefer cleanrom, cause its deoxed.

cleanrom is odexed

ota update to 4.1.1 bricked my phone.

i had plenty of battery life and was on 2.20 4.0.4 update prior to installing this OTA. now my phone wont even turn on after i did the update nor will it charge and have the light come on.. any ideas?

Let me guess. You had supercid??
Sent from my HTC One X using Tapatalk 2

if supercid gives problems on the at&t ota, then you should of been s-off cause i did ota fine with s-off and supercid.

idk i havent really heard of it but maybe. anyway to fix this now or ?

no fix

ps3kev said:
idk i havent really heard of it but maybe. anyway to fix this now or ?
Click to expand...
Click to collapse
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.

enduser76 said:
SuperCID is when you changed the CID on your phone to 1111111 when/if you tried to root your phone. Here's a brief explanation by another XDA poster.
Unfortunately, I am on the same boat you are, I did not change my CID from 1's back to it's original and the update bricked my phone. It own't power on or boot into anything, I'm crossing my fingers that the AT&T store will believe me when I say "I don't know what happened, can you fix it?" and give me a new phone.
Click to expand...
Click to collapse
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems. It could be, but given that some people don't have any problems, it could be anything.

tlazarus said:
It is not known if super-cid causes issues with doing an OTA! I have super-cid and s-off, and I applied the AT&T OTA without any problems after using the 2.20 RUU to go back to stock. It may be that super-cid causes issues if you are not s-off, but I don't think anyone really knows if it is definitely the presence of the super-cid that is causing the problems.
Click to expand...
Click to collapse
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.

redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?

romy134 said:
Hmm so if I had S-Off and Supercid and update via OTA sent directly from att not flashed any other way I will be ok?
Click to expand...
Click to collapse
If you were S-Off and SuperCID then the OTA should not affect you.
But. WHY are people wanting the stock OTA? It's causing issues because some people don't know if it's going to brick their phones. Please just wait until custom ROMs come based on the OTA. It's much much much easier

redpoint73 said:
S-off is precisely the reason you didn't brick. S-off by definition means that all security checks are bypassed, including CID check.
Click to expand...
Click to collapse
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.

I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium

The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
for the other images other then system that get updated, and with s-off now we don't really get screwed by anything so you might as well see if latest gives any improvements.

enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
People never listen or read up till its to late
Sent from my HTC One X using xda premium

enduser76 said:
Yup, now I (and hopefully people who read this thread) know better for next time.
I'm happy to report that AT&T swapped out my HTC One X for a new one and 4.1.1 is pretty sweet! I'm going to wait a while before unlocking and next time I'll make sure to have S-off
I found this thread useful, in that it gave me "closure" after trying desperately to revive my bricked phone for an hour. Got some Z's and woke up to a new phone - they couldn't turn it on at the AT&T service center and gave me a few examples of what could've happen. One of them was "using third party rom's" but they didn't accuse me of anything, they replaced my phone and I was on my way.
Click to expand...
Click to collapse
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.

DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
The guy at the service station didn't really ask me anything other than "what's wrong with your phone?" and I replied "it's not turning on." he said ok and plugged it into his machines and said he was going to run some tests and to take a seat. Five minutes later he said it's not turning on and he's going to replace it, I asked him what could've happen and he gave a few examples (including third party roms, etc) but that it could have been anything from a corrupt file to dropping it on the floor.
The_Zodiac said:
I seriously don't get why anyone updates ota. We have a flashable rom typically with a day
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
For me personally, I couldn't get most of the ROM's to work properly, if at all. I kept getting errors like " com.google.process.gapps has stopped working" or something similar and I'd have no phone service (for example) which is why I went back to stock.

DvineLord said:
were you honest or did you scam at&t cause that just makes at&t want to make security tougher and hurts other more preve people.
Click to expand...
Click to collapse
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF

c5satellite2 said:
Not true and they are the scammers btw.
Sent from the HOXL dimension of S-OFF
Click to expand...
Click to collapse
at&t customer service and even technical support have been badass for me last few years only issue is 110 bucks for my phone bill which imo should ive me the right to do whatever i want with my service and my phone without having to pay for tethering or getting throttled ever imo and cheaper early upgrades.

Can't Root Htc One XL 1.73

So, I've been trying to use this method to root by AT&T HTC One X
http://forum.xda-developers.com/showthread.php?t=1644167
Attached is the software information of my phone...
I run the .bat file and everything works and my phone reboots three times but then I try to load SuperSU but it says su binary code not installed which leads me to believe that the phone isn't rooted?
Any advice on how to get it to work?
Cheers,

What Hboot version do you have? Go into boot loader by turning the phone off, hold the volume down button and press the power button. Let us know what it says?
Sent from my One X using xda premium

subarudroid said:
what hboot version do you have? Go into boot loader by turning the phone off, hold the volume down button and press the power button. Let us know what it says?
Sent from my one x using xda premium
Click to expand...
Click to collapse
hboot-2.14.000

Did you buy that phone second hand? Is the bootloader locked? Unlocked? Relocked? Does it say s-on? Or S-off?
Sent from my One X using xda app-developers app

No, I bought it new. Its locked and s-on

akaeavaian said:
No, I bought it new. Its locked and s-on
Click to expand...
Click to collapse
Well that's odd since you're software says 1.73 but your hboot is of 3.18.
Sent from my One X using xda app-developers app

nah hboot is 2.14

Post a photo of your bootloader screen, because what you're describing is virtually impossible.
The only way you could be on hboot 2.14 and 1.73 software is if you got a refurb that was previously on 2.20 or earlier, was rooted, unlocked, s-off, had the 3.18 ruu run, then the 1.73 stock rom installed, then relocked and s-on, and no one at AT&T bothered to clean up the mess.

iElvis said:
Post a photo of your bootloader screen, because what you're describing is virtually impossible.
The only way you could be on hboot 2.14 and 1.73 software is if you got a refurb that was previously on 2.20 or earlier, was rooted, unlocked, s-off, had the 3.18 ruu run, then the 1.73 stock rom installed, then relocked and s-on, and no one at AT&T bothered to clean up the mess.
Click to expand...
Click to collapse
Lmao that's sounds exactly like what would happen.
Sent from my One X using xda premium

That sounds complicated
but here you go...

Looks like youre going to have to wait. no exploit for att on that version. Pisses me off that Rogers can still unlock and s-off. I want to say horrible things about att. Can we turn this into a AT&T bashing thread now?
Sent from my One X using xda premium

subarudroid said:
Looks like youre going to have to wait. no exploit for att on that version. Pisses me off that Rogers can still unlock and s-off. I want to say horrible things about att. Can we turn this into a AT&T bashing thread now?
Sent from my One X using xda premium
Click to expand...
Click to collapse
can telestra too? telus can aswell.

Again another reason to bash AT&T
Sent from my One X using xda premium

akaeavaian said:
That sounds complicated
but here you go...
Click to expand...
Click to collapse
I'm sorry, even seeing it, I don't believe it. I just don't see how this could be possible.
In any case, the 1.73 root method might work, but with that hboot, you can't change cid, and thus can't unlock or flash a custom recovery, which means you can't get permanent root. You're stuck where you are, wherever that is.

They don't send ota's for the hboot right? I was on 2.20 few and 1.14 hboot. And got it refurb back in December
Sent from my Carbon-ize Evita using xda-developers app

Ota does affect the hboot... Yes. But there's not an Ota that changes just the hboot. This must have been previously rooted. Most likely this phone was at some point unlocked and rooted, the person who returned it most likely updated to 3.18 after bootloader unlock/soff, had issues, Relocked and s-on, ruu to 1.73, returned to HTC where HTC fixed and repackaged without updating the software.
*edit* sorry that makes no sense.. Ruu would have downgraded the hboot too.. Just woke up -_-
We may never know what happened to thus phone lol.
Sent from my One X using xda app-developers app

exad said:
Ota does affect the hboot... Yes. But there's not an Ota that changes just the hboot. This must have been previously rooted. Most likely this phone was at some point unlocked and rooted, the person who returned it most likely updated to 3.18 after bootloader unlock/soff, had issues, Relocked and s-on, ruu to 1.73, returned to HTC where HTC fixed and repackaged without updating the software.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Aha! So it couldn't have been new. Unless he had warranty. something isn't right.
Sent from my Carbon-ize Evita using xda-developers app

Yup, he's got an ICS Rom with a locked 2.14 hboot. Now that's f'd up.

exad said:
We may never know what happened to thus phone lol.
Click to expand...
Click to collapse
I think it's possible to get that configuration:
-phone was originally on ICS
-root, unlock, and s-off
-apply 3.17 or 3.18 ruu to get 2.14 hboot. This would also remove the TAMPERED flag
-flash rooted stock 1.73 rom
-edit p3 or flash scotty's zips to relock and restore LOCKED text
-remove root
-restore s-on
-return phone to AT&T
I just don't see why anyone would do it or how it would survive the refurb process.

soo...err....is there anything I can do? I got it through Costco though...if that changes anything...

[Q] HTC One X AT&T out of options

Hello, I recently received an AT&T One X and the very first thing I did with it was try to root it and all that fun stuff. After a long adventure I couldn't get the HBOOT to upgrade so I had changed the CID to HTC__001 from cws_001 (I couldn't find this CID anywhere, but I swear that's what it said) and then the bootloader was re-locked. There is no OS, there is no recovery, I've tried 10 RUU's from Asia WWE to the UK RUU's and than all the AT&T ones I can find.
Most fastboot commands come back with a "Too many Links" error which I assume is from the bootloader being locked, and I cant change the bootloader's status because the bin file I got is for the supercid.
Please help me, I am usually quite proficient with this type of stuff but I really buried myself in a hole.

Why were you trying to upgrade your hboot..? Anyways.. What hboot do you have now? Is your Cid still htc__001?
Sent from my HTC One X using xda app-developers app

exad said:
Why were you trying to upgrade your hboot..? Anyways.. What hboot do you have now? Is your Cid still htc__001?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Isn't that cid for the international version?
Sent from my HTC One X using xda app-developers app

Re
My HBOOT is 1.14.0002. I tried to upgrade it for all the newer roms and such but thats when I managed to screw everything up. Yes, it is still HTC__001 and that is the international. I've tried several WWE RUU's and all refuse to work giving me various errors..

Yeah no ruu will work because you have an international cid with an at&t phone.
You'll need to htcdev over again and pray it works.
Sent from my HTC One X using xda app-developers app

I already unlocked the bootloader, It just wont let me do anything anymore... All fastboot commands are giving me either unknown errors or too many link errors.
I just dont understand why I cant change the CID anymore! The bootloader is unlocked so i should just be able to use fastboot..

koolgshizman said:
I already unlocked the bootloader, It just wont let me do anything anymore... All fastboot commands are giving me either unknown errors or too many link errors.
I just dont understand why I cant change the CID anymore! The bootloader is unlocked so i should just be able to use fastboot..
Click to expand...
Click to collapse
You can only change the cid once with fastboot oem writecid unless you are s-off
As for fastboot not working. Are you able to flash recovery?
Sent from my HTC One X using xda app-developers app

I managed to put on twrp but I didn't make a nandroids

koolgshizman said:
I managed to put on twrp but I didn't make a nandroids
Click to expand...
Click to collapse
Flash a stock-based ICS rom and then S-OFF, then you can change your cid, or whattever you need to do

Doesn't necessarily need to be ics but yeah you get the idea. After s-off then you can ruu to update your hboot and anything else that gets updates. Bear in mind that on aosp ROMs the touchscreen won't work after you upgrade until you downgrade the touchscreen firmware.
Sent from my HTC One X using xda app-developers app

Don't you still need supercid to s-off? Or is that no longer a requirement?

Never tried with am international or cid from another carrier.. Maybe it'll work? If not he can always hex edit his cid.
Sent from my HTC One X using xda app-developers app

Thank you for the replies, the link to the Hex editing of the CID saved me. I knew that's where the CID was located but I didn't know you could dd it out of the system. By the way, I was having hard times trying to flash CM9 on there and it didn't work, neither did viper roms so I was greatly discouraged. By the way, I have no earthly clue on how to S-OFF the One X so I will probably try to look harder for that. I'm probably going to either RUU to where I was, I believe 2.2 or put on.. some rom that sounds good. Any favorites? Y'all say I can flash ICS to it if I just flash the boot.img first right? I thought that the partition sizes would cause a conflict.. Oh well, I'll give it a try

koolgshizman said:
Thank you for the replies, the link to the Hex editing of the CID saved me. I knew that's where the CID was located but I didn't know you could dd it out of the system. By the way, I was having hard times trying to flash CM9 on there and it didn't work, neither did viper roms so I was greatly discouraged. By the way, I have no earthly clue on how to S-OFF the One X so I will probably try to look harder for that. I'm probably going to either RUU to where I was, I believe 2.2 or put on.. some rom that sounds good. Any favorites? Y'all say I can flash ICS to it if I just flash the boot.img first right? I thought that the partition sizes would cause a conflict.. Oh well, I'll give it a try
Click to expand...
Click to collapse
You should be able to flash any rom so long as you fastboot flash the boot.img ics or jb.

A million thanks, well, I thanked you once, that should suffice. I'm almost set now, for a second I thought the phone would be a goner.

If you can get to bootloader your phone can be saved. Good luck, have fun.
Sent from my HTC One X using xda app-developers app

Yes, CM10.1 is now running, I'm just waiting for my gapps.. thanks again

(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