Database Info

[POLL] What HBOOT Version Are You Running?

Hey everyone,
It's come to my attention by a particular individual that our phone has shipped with two (or more?) HBOOT versions. If you could please let me know what version your phone is running by voting on the poll I would appreciate it. This is important for S-OFF exploit purposes.

not seeing the poll yet (I realize you just posted this), but my hboot version:
1.44.0007

Another 1.44.0007
and MICROP-0353

I think you should put the procedure to check the HBOOT just in case some people don't know.

1.44.0007..........

beamer786 said:
I think you should put the procedure to check the HBOOT just in case some people don't know.
Click to expand...
Click to collapse
Power down phone.
Remove battery.
Wait 5 seconds.
Re-insert battery.
Hold down VOLUME DOWN button while powering on phone.
This will bring up the H-BOOT screen. If you have quick start turned off you probably don't have to remove the battery but this is a pretty fool-proof way to get into H-BOOT.

1.44.0007 for my T-Mobile retail phone

1.44.0007 hboot

Nice to see that revolutionary came through for the mt4gs... I hade a feeling it would
1.44.0007
Sent from my myTouch_4G_Slide using XDA App

sounds like everyone thus far has the 1.44.0007 H-BOOT. Hopefully this makes things easier for the devs!?!

Hboot - 1.44.0006

nyolsson said:
Hboot - 1.44.0006
Click to expand...
Click to collapse
EDIT: Just upgrade to the RUU posted in the development section BEFORE attempting the exploit method to be released soon. It will require HBOOT 1.44.0007. http://www.filefactory.com/file/cc6...0U_10.12.9007.07_M2_release_201815_signed.zip

nyolsson said:
Hboot - 1.44.0006
Click to expand...
Click to collapse
you're already running the S-Off bootloader. no one with 1.44.0007 has S-OFF that I'm aware of.

pmcqueen said:
you're already running the S-Off bootloader. no one with 1.44.0007 has S-OFF that I'm aware of.
Click to expand...
Click to collapse
Wow. I missed that, hah. Thanks for the correction.

pmcqueen said:
you're already running the S-Off bootloader. no one with 1.44.0007 has S-OFF that I'm aware of.
Click to expand...
Click to collapse
okay.. just answering the poll.

nyolsson said:
okay.. just answering the poll.
Click to expand...
Click to collapse
I know. I just didn't want anyone to think there were actually 3 S-ON bootloaders floating around, considering the purpose of this thread was to help prepare for S-OFF via revolutionary.

Seems pretty unanimous so far.

If x.0006 is the S-Off Hboot, and x.0007 is the S-On that we all seem to have, what is 1.44.1107? Is there another version of this phone out there somewhere?
Edit: This seems to be the version you have after Rev S-Off

i have the 006 hboot as well (device was from an HTC training event). has any one procured root and flashed CWM with out S-ON'ing a device with the new bootloader, then running revolutionary? seems like going backwards to me...

No its not backwards. It works just fine. Just follow the directions here: http://revolutionary.io
Sent from my MyTouch 4G Slide using xda premium

[Q] Someone knows how to install the (RUU 3.17.707.2 JB) in the HTC One X AT&T

Start telling them already installed the versions (RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2) and
(RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2) on my HTC One X AT&T.
This could by having the 'superCID' and re-locked.
My problem is now when I try to install the version (RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1) the application
gives me the error (HTC Error 31) but this not happened to me with previous versions.
NOTE: I now that the HTC Error 31 is because it is the device's original RUU.
Anyone know how to fix this?
I read somewhere that there is a problem with the 'superCID'. They know about this?
Or any solution using the (OTA_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1)?
NOTE: I also know that there is a type of encryption in ROM.zip for JB
I appreciate the help
Thanks
I create a new thread because I can not find where this the same case with some solution for this.

Unless we have soff we can only flash our carriers ruu's so you're stuck on ics unless you root

a box of kittens said:
Unless we have soff we can only flash our carriers ruu's so you're stuck on ics unless you root
Click to expand...
Click to collapse
Wrong, supercid will let any RUU flash. You could also change the CID to simply match that of the RUU as well, 3.17.707.1 is expecting HTC__044.
3.17.707.1 RUU that is floating around on the internet is known to be broken and simply does not work.

Re: [Q] Someone knows how to install the (RUU 3.17.707.2 JB) in the HTC One X AT&T
twistedddx said:
Wrong, supercid will let any RUU flash. You could also change the CID to simply match that of the RUU as well, 3.17.707.1 is expecting HTC__044.
3.17.707.1 RUU that is floating around on the internet is known to be broken and simply does not work.
Click to expand...
Click to collapse
I could swear turge fixed one and posted it. But from what I understand ruu's don't like supercid and may brick your phone.
*edit* never mind I'm dumb that's just a flashable zip not an ruu.
Sent from my One X using xda app-developers app

twistedddx said:
Wrong, supercid will let any RUU flash. You could also change the CID to simply match that of the RUU as well, 3.17.707.1 is expecting HTC__044.
3.17.707.1 RUU that is floating around on the internet is known to be broken and simply does not work.
Click to expand...
Click to collapse
And how it could change my CID (superCID 11111111) to HTC__044?
Or any solution using the OTA RUU.
Thanks :good:

twistedddx said:
Wrong, supercid will let any RUU flash. You could also change the CID to simply match that of the RUU as well, 3.17.707.1 is expecting HTC__044.
3.17.707.1 RUU that is floating around on the internet is known to be broken and simply does not work.
Click to expand...
Click to collapse
I see...so everything would go smoothly if the cid was that?

Re: [Q] Someone knows how to install the (RUU 3.17.707.2 JB) in the HTC One X AT&T
a box of kittens said:
I see...so everything would go smoothly if the cid was that?
Click to expand...
Click to collapse
So long as bootloader was locked, hboot is not newer than ruu to be flashed, last ota or ruu Rom version is not newer than ruu to be flashed and that it is not 3.17.707.1 ruu as it is broken.
But yes cid is what blocks ruu from other regions, it is the reason why supercid is desired.
Supercid doesn't brick phones, or at least not in 99% of cases. Those that bricked with supercid need to be pay more attention to what they really did, as I bet the issue will be found somewhere else, Eg in their method, other mods, hardware failure, etc.
Supercid is done so your phone has an "all" region so you can flash a ruu or ota from anywhere. Those claiming it causes bricks are going against what Htc created supercid for.
---------- Post added at 11:37 PM ---------- Previous post was at 11:34 PM ----------
exad said:
I could swear turge fixed one and posted it.
Click to expand...
Click to collapse
Turge can't fix a ruu, he does not have access to the tools required. And if he did he definately would not be using them to fix a ruu for the public.
Turge used ota updates for the base of his viperxl and also posted a stock system image of an ota base also.

Excuse me for sounding stupid but grey matter not working

I have been flashing for some time but excuse me if I sound stupid but the grey matter just don't work any more. I have RUU'd different RUU's from the 1.82 to 2.20 trying to get different customs to work and I can't figure out what base I am on. At the time I am using Clean Rom 6.1 R2 and things seem to work fine but just wondering. Some how I managed to go from HBOOT 2.14 I think down to HBOOT 1.09 without downgrading. I think I got it from some RUU. I have read that the HBOOT 1.09 is a golden thing on the phone but don't know why.
With this rom I have tried to flash the 3.18 radio and get a soft brick at the boot screen. I am pretty sure the last time I RUU'd I used the Cingular Us 1.82 and in the process it upgraded itself to the 1.83 . Now I have read that some roms with sense work better on the 3.18 RUU.. Will I loose the HBOOT 1.09 if I do this?
At the present
S-OFF
unlocked
CID 11111111
radio 0.24p..32.09.0501.......
I am just looking and trying different variations to find the best setup for my phone. Excuse me for sounding so stupid. The grey matter just is slush any more.

The 3.18 ruu will give you the 2.14 hboot but sense you are s-off which hboot you have is not that important people wanted the 1.09 hboot because you could flash radios and boot.img with it s-off allows you too do this no matter what hboot you have
Sent from my HTC One X using Tapatalk 2

Because you're s-off it doesn't matter what hboot you're on. Sense ROMs tend to run smoother/better with the latest update. So feel free to RUU up to 3.18. Don't relocked your bootloader, just ruu.
If you want to run AOSP ROMs after, though, you'll need to downgrade your touchscreen firmware.
Also for some people cm10 doesn't boot until they've upgraded for some odd reason.
Sent from my HTC One XL using xda app-developers app

exad said:
Because you're s-off it doesn't matter what hboot you're on. Sense ROMs tend to run smoother/better with the latest update. So feel free to RUU up to 3.18. Don't relocked your bootloader, just ruu.
If you want to run AOSP ROMs after, though, you'll need to downgrade your touchscreen firmware.
Also for some people cm10 doesn't boot until they've upgraded for some odd reason.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I understand that being S-OFF one could do most anything and be safe but I didn't really know if loosing the HBOOT 1.09 had any consequents or not. Plus, didn't know if upgradeing to the 3.18 firmware would be that beneficial or not. At one point I was on the 2.20 and took the OTA ATT udgrade to see what it was about but didn't like the rom ,but I did downgrade the touch screen . There are features with all the customs but don't like any one in particular, wish there some way to combine certain features from each one into one to make one that I liked for my phone. So far the best I can come up with is Clean Rom 6.1R2 with BlueIceSense CR6 and cityID apk. plus the radio from 3.18.
Thanks for understanding loss of grey matter stupidity

[Q] HTc One X (at&t) Updating Error (155)

Good Day,
I recently tried to update my HTC One X (at&t) phone using the manual installation process as I am unable to do it OTA. I downloaded the RUU from HTC suport site and followed all the instructions but whenever the process reaches 29% in updating sysytemit gives me the error code (155) unkown error. The progress bar on the phone fills up green and at the end of the bar there is a small triangle with an exclamation mark at the end. That is not all when I unplug the phone it shows the HTC logo with four exclamation marks, one in each corner. And the phone doesn't turn on at all, no matter how much I try rebooting it. I have tried the installation process a number of times with the same result. How can I resolve this problem and How can I get my phone to turn on as normal. Please help me . I really love this phone my wife bought it for me just two months ago.
Yours Kindly
Roger Fontenelle

More info needed. Was the phone modified at all before you were doing this? Which RUU were you using? What were your bootloader details?
Sent from my Evita

Freakyfonty said:
Good Day,
I recently tried to update my HTC One X (at&t) phone using the manual installation process as I am unable to do it OTA. I downloaded the RUU from HTC suport site and followed all the instructions but whenever the process reaches 29% in updating system it gives me the error code (155) unknown error. The progress bar on the phone fills up green and at the end of the bar there is a small triangle with an exclamation mark at the end. That is not all when I unplug the phone it shows the HTC logo with four exclamation marks, one in each corner. And the phone doesn't turn on at all, no matter how much I try rebooting it. I have tried the installation process a number of times with the same result. How can I resolve this problem and How can I get my phone to turn on as normal. Please help me . I really love this phone my wife bought it for me just two months ago.
Yours Kindly
Roger Fontenelle
Click to expand...
Click to collapse
The bootloader is locked. I used the RUU from the HTC support site. I recently used this Ruu htc_one_x_RUU_2.20.502.7_att_us_08022012. I have gotten a little further the process now reaches 43% and says image update failure error 159.

Ok, but the question was has the phone been modified at all before? I guess you don't know what the bootloader details are/were?
Sent from my Evita

timmaaa said:
Ok, but the question was has the phone been modified at all before? I guess you don't know what the bootloader details are/were?
Sent from my Evita
Click to expand...
Click to collapse
The most I can get from this is Bootloader
(bootloader) cid: 11111111
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\FREAKYFONTY\Desktop\One_X_ATT_All-In-One_Kit_v3.0.1\One_X_ATT_All-In-On
e_Kit_v\data>
I used the All in one kit to get this infor version 3.0.1
This is what i get after i unplugged the phone
EVITA PVT SHIP S-OFF RL
CID 11111111
HBOOT-1.08.0000
RADIO-O.19as.32.09.11_2
OPENDSP-V29.1.0.45.0622
eMMC-boot
MAR 21 2012,16:01:09
RUU

Ok so the phone has been modified. Whatever you do, do not run any RUU higher than 2.20, it will brick your device. Do you happen to know what firmware version the phone was on before attempting to run the RUU? And what is the purpose of running the RUU?
Sent from my Evita

timmaaa said:
Ok so the phone has been modified. Whatever you do, do not run any RUU higher than 2.20, it will brick your device. Do you happen to know what firmware version the phone was on before attempting to run the RUU? And what is the purpose of running the RUU?
Sent from my Evita
Click to expand...
Click to collapse
RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio_0.19as.32.09.11_2_10.105.32.25L_release_271865_signed
I ran this RUU and got it to work, thanks very much for attending to my post. Just t one question, how can i update this phone to the htc sense 4+ or jelly bean 4.1 and what do you mean by modified? My phone is unlocked that's how i got it out of the box. It's has at&t app on it but not registered to at&t as I am out of the US.

I'm not sure where you bought the phone, but it wasn't brand new. There are a few signs of this. Firstly, if the phone was brand new it would be on a much later/newer firmware/software version than it was. Next, the phone is s-off, the likelihood of the phone being shipped out of the factory like that is extremely low (I've seen only one case). Lastly, the phone has SuperCID (11111111 as opposed to CWS__001), the likelihood of the phone shipping out of the factory like that is also extremely low.
Does the phone have the HTC logo at the top of the screen or the at&t logo?
Sent from my Evita

timmaaa said:
I'm not sure where you bought the phone, but it wasn't brand new. There are a few signs of this. Firstly, if the phone was brand new it would be on a much later/newer firmware/software version than it was. Next, the phone is s-off, the likelihood of the phone being shipped out of the factory like that is extremely low (I've seen only one case). Lastly, the phone has SuperCID (11111111 as opposed to CWS__001), the likelihood of the phone shipping out of the factory like that is also extremely low.
Does the phone have the HTC logo at the top of the screen or the at&t logo?
Sent from my Evita
Click to expand...
Click to collapse
No actually the only time I see the at&t logo is when it's starting up and on the apps on the phone. Bought it on Amazon it said new

It's definitely a used phone, I hope you didn't pay too much for it. If you want to update it to 4.1 and Sense 4+ you can use the at&t 3.18 RUU, upon closer inspection of your bootloader details you have s-off so it's completely safe to do so. I didn't notice you had s-off earlier when I advised you not to do so, apologies for that.
Sent from my Evita
---------- Post added at 01:24 AM ---------- Previous post was at 01:18 AM ----------
EDIT: Actually, if you want Wi-Fi tethering/hotspot to work you should not use the at&t 3.18 RUU, use the HTC/Singtel/Starhub Singapore 3.17 RUU, you'll find it here:
http://forum.xda-developers.com/showthread.php?t=
Sent from my Evita

timmaaa said:
It's definitely a used phone, I hope you didn't pay too much for it. If you want to update it to 4.1 and Sense 4+ you can use the at&t 3.18 RUU, upon closer inspection of your bootloader details you have s-off so it's completely safe to do so. I didn't notice you had s-off earlier when I advised you not to do so, apologies for that.
Sent from my Evita
---------- Post added at 01:24 AM ---------- Previous post was at 01:18 AM ----------
EDIT: Actually, if you want Wi-Fi tethering/hotspot to work you should not use the at&t 3.18 RUU, use the HTC/Singtel/Starhub Singapore 3.17 RUU, you'll find it here:
http://forum.xda-developers.com/showthread.php?t=
Sent from my Evita
Click to expand...
Click to collapse
It's rather unfortunate that it's a used phone I put so much effort into research on this phone before I bought it. It was under the new section that why I purchased it my wife don't like buying used item especially phones. Paid $330US for it. So what you are saying to me is that as I have installed the ics on it version4.0 I can update using the link you privided. Here are the details of the phone.
Android Version 4.0.4
HtC Sense Version 4.0
Software number 2.20.502.7710RD
HTC SDK API LEVEL 4.23
HTC EXTENSION VERSION 403_1_GA_20

It is a shame, but as long as it all works ok I wouldn't worry too much. For some reason the whole link didn't post properly before so here it is again:
http://forum.xda-developers.com/showthread.php?t=1671237
That's the RUU Collection thread, you'll find links to many RUUs there, but the one that's probably best for you if you want 4.1 and Sense 4+ is the HTC/Singtel Singapore 3.17 RUU.
Android 4.2.2 and Sense 5 is available for our phones too now, you can take an OTA update after running the RUU to get that.
Sent from my Evita

timmaaa said:
It is a shame, but as long as it all works ok I wouldn't worry too much. For some reason the whole link didn't post properly before so here it is again:
http://forum.xda-developers.com/showthread.php?t=1671237
That's the RUU Collection thread, you'll find links to many RUUs there, but the one that's probably best for you if you want 4.1 and Sense 4+ is the HTC/Singtel Singapore 3.17 RUU.
Android 4.2.2 and Sense 5 is available for our phones too now, you can take an OTA update after running the RUU to get that.
Sent from my Evita
Click to expand...
Click to collapse
Thaks very much for your assistance, you have proven yourself invaluable by your contributuion towards my situation. Jus t one more question. As you have suggested. The HTc singetel Ruu that you suggested I use, would take me to Android 4.1 with HTC sense 4+ with no problems and then from there I can update ota for Android 4.2.2 with HTc Sense 5.

Taking an OTA on a modified phone can be somewhat risky, I don't have any first-hand experience but I believe you'd need to change your CID to the CID that the OTA is looking for, and have stock recovery. In my opinion it's probably a better idea to unlock your bootloader again, install TWRP recovery, and flash one of the many Android 4.2.2 Sense 5 ROMs we have available in our development section.
Part of the beauty of having the unlocked bootloader is that you can easily flash a different ROM if you decide you want a change. You'll have dozens of ROMs to choose from, from Sense to aosp. Plus many features that a stock phone just can't offer.
Sent from my Evita

Current OTA's will install correctly if:
1)s-off (required with supercid to prevent bricks but otherwise not required)
2)supercid (or valid cid for ruu/ota)
3)locked bootloader
4)RUU to desired base (this will also give you the correct recovery at the same time)
5)accept ota
Edit:
oh also:
6)I believe the mid should match unless you are s-off/supercid also.

Freakyfonty said:
It's rather unfortunate that it's a used phone I put so much effort into research on this phone before I bought it. It was under the new section that why I purchased it my wife don't like buying used item especially phones. Paid $330US for it.
Click to expand...
Click to collapse
Was it from Amazon directly, or a 3rd party that sells via Amazon? Either way, if it was explicitly describes as new (and not used or refurbished), I would contact the seller and seek at least a partial refund based on an incorrect or even fraudulent description. The phone is almost certainly used, as its SuperCID and S-off. And $330 is a lot to pay for a used AT&T One X. The going rate for this device used on eBay seems to be $200, give or take.
If such resolution by the seller is important to you, I'd advice looking into it before any further modification of the phone.
---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------
timmaaa said:
Taking an OTA on a modified phone can be somewhat risky, I don't have any first-hand experience but I believe you'd need to change your CID to the CID that the OTA is looking for, and have stock recovery. In my opinion it's probably a better idea to unlock your bootloader again, install TWRP recovery, and flash one of the many Android 4.2.2 Sense 5 ROMs we have available in our development section.
Part of the beauty of having the unlocked bootloader is that you can easily flash a different ROM if you decide you want a change. You'll have dozens of ROMs to choose from, from Sense to aosp. Plus many features that a stock phone just can't offer.
Click to expand...
Click to collapse
I would agree with this. As long as you research and are comfortable with what root and unlocked bootloader mean, I'd say that having a modified phone is much better than returning to stock AT&T software.

redpoint73 said:
Was it from Amazon directly, or a 3rd party that sells via Amazon? Either way, if it was explicitly describes as new (and not used or refurbished), I would contact the seller and seek at least a partial refund based on an incorrect or even fraudulent description. The phone is almost certainly used, as its SuperCID and S-off. And $330 is a lot to pay for a used AT&T One X. The going rate for this device used on eBay seems to be $200, give or take.
If such resolution by the seller is important to you, I'd advice looking into it before any further modification of the phone.
Click to expand...
Click to collapse
I agree totally. The phone is definitely second-hand, not only is it SuperCID and s-off but it's also running an at&t ROM on a non at&t device. I'd be hounding for a partial refund.
Sent from my Evita

timmaaa said:
I agree totally. The phone is definitely second-hand, not only is it SuperCID and s-off but it's also running an at&t ROM on a non at&t device. I'd be hounding for a partial refund.
Sent from my Evita
Click to expand...
Click to collapse
I want to express my thanks profusely to you guys for helping me out with my problems. You'll are truly great thanks so much. Sorry can't find the thanks button (lol) must be going blind. Contacted the store will let you know what they say. Not very hopeful on a positive response especially in the refund department. THANKS AGAIN

Freakyfonty said:
I want to express my thanks profusely to you guys for helping me out with my problems. You'll are truly great thanks so much. Sorry can't find the thanks button (lol) must be going blind. Contacted the store will let you know what they say. Not very hopeful on a positive response especially in the refund department. THANKS AGAIN
Click to expand...
Click to collapse
3rd party seller on Amazon? If they don't offer any way to remedy the problem, threaten to escalate the issue and report them to Amazon as a fraudulent merchant.
If they are a reputable seller, they should make good on this. If they aren't reputable, no reason to play nice. Report them and give them negative feedback.

Freakyfonty said:
Thaks very much for your assistance, you have proven yourself invaluable by your contributuion towards my situation. Jus t one more question. As you have suggested. The HTc singetel Ruu that you suggested I use, would take me to Android 4.1 with HTC sense 4+ with no problems and then from there I can update ota for Android 4.2.2 with HTc Sense 5.
Click to expand...
Click to collapse
Hey Timaaa,
Can't seem to find the RUU that you suggested in the thread, Is it possible that you can send me the direct link to get the HTC/Singtel Singapore 3.17 RUU. Thanks a lot. The site doesn't seem to be working anymore or is not responding. busylawson.com shows problem locating page.

[Q] HTC One X Need RUU (Cant Find CID AT ALL/11111111) Need Stock!

Hello everybody! I need help urgent! I have my AT&T HTC One X (XL according to my "Settings" "Model Number" and I need to restore back to stock. I'll list everything that is wrong, I need help with, and more settings on my device. MAINLY, IF ANYBODY CAN AT LEAST HELP ME TO FIND MY CID AS SOON AS POSSIBLE, THAT'S ALL I NEED AS FAR AS I KNOW RIGHT NOW.
My Device Settings:
1. Android Version: 4.1.1
2. I did successfully flash to "MIUI-3.8.9" using "Hasoon2000's HTC One X (Evita) All-In-One Toolkit" for most of this.
3. HBOOT/Bootloader:
*** TAMPERED ***
***RELOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
4. RECOVERY:
ClockworkMod Recovery v6.0.3.1
Notes:
1. I looked at the video on youtube, "TUTORIAL: HTC One X stock ROM update: 4.1.1 to 4.2.2 (via CWM)" using CWM (same version) but kept getting status error 0 no matter whether odexed or deodexed.
2. I tried using fastboot options I saw on other posts on this website to find your stock CID, but it still showed 11111111.
3. I used "Hasoons200's Toolkit" to SuperCID to 11111111.
4. "Xfactor" on the toolkit to exploit the device's CID.
Help With:
1. To at least get/find out a way to find out my TRUE STOCK CID as quick as possible.
2. To find the RUU used for this device.
I truly thank all of you for your help!

If your phone is an at&t model the original CID is CWS__001. Your CID doesn't actually matter anyway because you're s-off, you can run any Evita RUU without any problems regardless of your CID. The reason fastboot commands were showing your CID as 11111111 is because your CID is 11111111, that's because SuperCID overwrites the original CID.
There's nothing at all "wrong" with your device. I think you're extremely confused. I'm not sure why you've been trying all those toolkits, those give you SuperCID, they don't reverse it. You seem to lack a basic understanding of this device, modifying it, and what you can and can't do with it. Why exactly do you want to return to stock? I can tell you exactly how to do it but I'd like to know why first.
Sent from my Evita

timmaaa said:
If your phone is an at&t model the original CID is CWS__001. Your CID doesn't actually matter anyway because you're s-off, you can run any Evita RUU without any problems regardless of your CID. The reason fastboot commands were showing your CID as 11111111 is because your CID is 11111111, that's because SuperCID overwrites the original CID.
There's nothing at all "wrong" with your device. I think you're extremely confused. I'm not sure why you've been trying all those toolkits, those give you SuperCID, they don't reverse it. You seem to lack a basic understanding of this device, modifying it, and what you can and can't do with it. Why exactly do you want to return to stock? I can tell you exactly how to do it but I'd like to know why first.
Sent from my Evita
Click to expand...
Click to collapse
Yeah I do have AT&T. Also, yes, I'm pretty new at rooting and such, but I am still learning
I forgot to add this in the post, will edit it in, that I am using "MIUI" like said, and I decided I wanted to get another rom. I tried to get "Paranoid Android", latest version, boot-loader both unlocked and locked, and TWRP and CWM recovery. It came up with status 0 (having to do with the update-binary) but luckily I made a nandroid backup. The device is still working from the nandroid backup, but I will probably use the CID (CWS__001) to get the stock RUU endeavor, then flash.

Eh.. You have an evita, not endeavor. If you flash endeavor stuff you will likely brick.
Sent from my HTC One XL using xda app-developers app

exad said:
Eh.. You have an evita, not endeavor. If you flash endeavor stuff you will likely brick.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok. IS there anyway to know which RUU I would need to get stock without CID? If you need any information to help me with this (such as rom version I'm currently using and such) I'll let you know.

Antm50jr said:
Yeah I do have AT&T. Also, yes, I'm pretty new at rooting and such, but I am still learning
I forgot to add this in the post, will edit it in, that I am using "MIUI" like said, and I decided I wanted to get another rom. I tried to get "Paranoid Android", latest version, boot-loader both unlocked and locked, and TWRP and CWM recovery. It came up with status 0 (having to do with the update-binary) but luckily I made a nandroid backup. The device is still working from the nandroid backup, but I will probably use the CID (CWS__001) to get the stock RUU endeavor, then flash.
Click to expand...
Click to collapse
The installer for Paranoid Android probably failed because the ROM wasn't meant for this phone, you got lucky it didn't brick you. You have the Evita, not the Endeavoru, I'm not sure where you're downloading your ROMs from but it's the wrong place. Only ever download ROMs from within this device forum you're posting in now, NEVER anywhere else.
Sent from my Evita
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
Antm50jr said:
Ok. IS there anyway to know which RUU I would need to get stock without CID? If you need any information to help me with this (such as rom version I'm currently using and such) I'll let you know.
Click to expand...
Click to collapse
You have s-off so you can run any Evita RUU that you want, your CID doesn't matter when you have s-off. Go to androidruu.com and get one from there, just make sure it's from the Evita section. I still have no idea why you want to RUU though, you said you just want to change ROMs, an RUU will return your phone to being completely stock.
Sent from my Evita

timmaaa said:
The installer for Paranoid Android probably failed because the ROM wasn't meant for this phone, you got lucky it didn't brick you. You have the Evita, not the Endeavoru, I'm not sure where you're downloading your ROMs from but it's the wrong place. Only ever download ROMs from within this device forum you're posting in now, NEVER anywhere else.
Sent from my Evita
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
You have s-off so you can run any Evita RUU that you want, your CID doesn't matter when you have s-off. Go to androidruu.com and get one from there, just make sure it's from the Evita section. I still have no idea why you want to RUU though, you said you just want to change ROMs, an RUU will return your phone to being completely stock.
Sent from my Evita
Click to expand...
Click to collapse
I can't believe this! It turns out, it's bricked I think! I tried to restore from a nandroid backup I got off the internet, not sure whether it was evita or not, WAS ON THIS WEBSITE (XDA), and not it won't boot. The screen is on, but it shows the white screen HTC logo with red letters under it, and made a low buh-buh sound when in USB. I cant find a way to enter boot-loader or recovery (computer cant detect it) but it does show the solid red light at the top. Please, even if it involves downloading a ton of computer applications, I'm willing to.

I can believe it. Why the hell did you restore a nandroid if you're not even sure if it was for Evita? Have you not listened to a word we've been saying to you? I'm not sure why I bothered trying to help you if you're ignoring the advice I'm giving. Your phone isn't bricked, if it turns on it isn't bricked. Do some research and figure out how to recover.
Sent from my Evita

timmaaa said:
I can believe it. Why the hell did you restore a nandroid if you're not even sure if it was for Evita? Have you not listened to a word we've been saying to you? I'm not sure why I bothered trying to help you if you're ignoring the advice I'm giving. Your phone isn't bricked, if it turns on it isn't bricked. Do some research and figure out how to recover.
Sent from my Evita
Click to expand...
Click to collapse
I just wanted to say that I am sorry, and I did fix the problem. Thank you for your support! You are right: I should have listened and pay more attention. Thank you though! I'll always check to see whether a rom is Evita or Endeavor.