Database Info

[Q] UnROOT my HTC DESIRE.

Hi guys, i received a DESIRE S, but this phone has been with other guy that sells me that phone.
Now i think its rooted because i downloaded the "ROOT CHECKER" on the market and it says "yes" that im rooted. Then i did de power button and volume down, and i got this:
SAGA PVT ENG S-OFF
HBOOT-0.98.2000 (PG8810000)
RADIO-38.03.00.03_M
eMMC-boot
I dont know what method to root was used
I think im with the sock rom because when i turn on my phone, it just show htc logo then starts normally (pin code, etc)
Ill give more information about my phone:
software number 1.12.0.0
Is that a way to unroot my phone? PLEASE
I have read some threads of other guys trying this but theyr hboot's are differents of mine, so im scared of brick my phone
Can any1 tell me step by step to unroot my phone? i have no experience with root's and this things
EDIT: Sorry for my bad english. Im Portuguese.

It looks like he unlocked the phone with the ENG HBOOT of HTC. This version of HBOOT is for the service personnel and was then released by HTC.
AFAIK you can simply flash a RUU ROM which will unroot the phone. But it won't change that it is S-OFFed. Root and S-OFF are different things. But normally it won't matter in all-day use if your phone is S-OFFed.

It was S-OFFed by Revolutionary then an ENG bootloader was flashed on it. Returning to Stock is pretty easy in your situation.
First you need to find your real software version:
1) follow the guide about adb and fastboot in my signature (make sure that you have USB Debugging ON in your Settings -> Applications -> Development)
2) connect the device to PC, open command prompt and type:
Code:
adb devices
{your serial number should appear}
adb reboot bootloader
{the phone will reboot}
fastboot devices
{your serial number should appear}
fastboot getvar version-main
the number obtained from the last command is the real one. You can leave your phone connected and go to the "Shipped Desire S ROM collection" thread (it is sticky in the Android Development subforum here). Find a RUU with the same number as yours, download it, start the exe on your PC and follow the instructions. Keep in mind that this will DELETE all you personal data and applications!. After completion you will have completely Stock device and you can check for updates, I believe you will get the latest Sense 3.0 Good luck, if any questions post here.

OMG, you are my GOD!
I'll read everything in your signature, then i will start the process.
One question: Doing all this, im unrooted and s-on? Because all i want are the official updates and with s-off i think i can't update, or can i?
eheh, i'm really appy with your answer

When i type the last command:
"fastboot getvar version-main", it says: < waiting for device >
something wrong?
i can do the commands "adb", "adb devices", but the "fastboot devices" dont appear, why?
what im doing wrong?

Forget my post over there /\
i got the number 1.21.0.0
ill search a ruu with this number, thanks !! :d

Desire S said:
Forget my post over there /\
i got the number 1.21.0.0
ill search a ruu with this number, thanks !! :d
Click to expand...
Click to collapse
hmmm. there is no such as far as I know
Do you have an update notification?
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Tell me the output of this command:
Code:
fastboot getvar cidnum

No updates
I got the number in cidnum: 11111111 :s
I can't find any RUU, my software number is strange

Desire S said:
No updates
I got the number in cidnum: 11111111 :s
I can't find any RUU, my software number is strange
Click to expand...
Click to collapse
I think that you can use whatever RUU you like
this cidnum is called super cid - you can flash anything on it
the version number (that is also checked by the Rom Update Utility, or so called RUU) is the lowest possible - so again you can flash anything on it
So you just have to choose one of the RUU provided that suits you best and use it - if you are from the Europe I suggest to flash directly 2.10.401.8 - you will have the latest version. If from other region - choose accordingly.
{just a reminder: if you just want Sense 3.0 there is no need to remove root - you can flash a the latest prerooted stock ROM and have all benefits of the Stock system, BUT will keep the option to change to the forthcoming ICS or Sense 3.5 ROM which most probably will never arrive officialy for our devices. Think about it }

When i run this RUU, whas specifics will have my phone?
Now i got this:
SAGA PVT ENG S-OFF
HBOOT-0.98.2000 (PG8810000)
RADIO-38.03.00.03_M
eMMC-boot
When i run the ruu, what i ill get? s-on?
All i want are thhe official updates :s (2.3.5 and sense 3.0)
And can you paste there the ruu that you think is the best for my software number?
oh, and thanks for everithing, is there a way to give a "positive reputation"??
and what you think about my english? its "ok" right?
EDIT: I'M from portugal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so maybe this can help you choosing the best RUU for me
thanks again
EDIT2: I bought this phone at 1 guy, so i don't know the right localization of the phone :S

1) the RUU will get you S-ON (in fact complete Stock like you just got it from the shop)
2) you will get latest 2.3.5, Sense 3.0 update when flashing this RUU - it has Spanish locale
3) there is a THANKS button at the bottom of my posts
4) your English is fine, I can understand you perfectly, I hope my English is the same for you

One more question :
When people root their desire s, they should have the app of "super user" right?
Mine dont have this app. This means that mine is not rooted and just are s-offed?

Don't ask me why but when I received my phone it had s-off!

Desire S said:
One more question :
When people root their desire s, they should have the app of "super user" right?
Mine dont have this app. This means that mine is not rooted and just are s-offed?
Click to expand...
Click to collapse
You can always use SuperOneclick to push Superuser to your phone. Or try to install it from the Market

Hey amida, i was thinking, and i think i want to go to reaper v.1.1 rom. So i downloaded the rom manager in market then flash but i got a error: something like "privilege commands" this meand that im just s-off and not rooted?
So i want to root my phone, can you tell-me the best guide for my hboot? PLEASEEE

I have installed the superuser on the market but when i open i got no apps in there. When i click "flash clockworkmod revoery" i got the error "privileged commands". When i do the power button and volume down, i'm sure that im s-off and got this:
SAGA PVT ENG S-OFF
HBOOT-0.98.2000 (PG8810000)
RADIO-38.03.00.03_M
eMMC-boot
I cant understand if im rooted or not

Follow this thread
[INFO] After Revolutionary (S-OFF) Install Clockworkmod, root & more
from my Desire S using XDA Premium

[Q] Some questions about HOX ATT CID, bootloader & LTE

Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
6./ In the thread radio & RIL , I read that update 2.2x will replace HBOOT and make old radio not compatible, is it because new HBOOT resize the radio partition smaller? So if I flash a custom rom based on Asia RUU 2.29 for example (not the dreaded 2.20 ATT), my current HBOOT will be replaced by new HBOOT as well? With no S-OFF, we can not flash HBOOT so will I be stuck with the new HBOOT and therefore, new radio roms only?
Looking forward to hearing from HOXL gurus. Thanks.

linhldz said:
Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
Click to expand...
Click to collapse
1. Spoofed CID is permanent unless you go in and change it back. For all intents and purposes, it's permanent.
2. Actually to run an RUU, you must relock your bootloader or it will fail. As long as you have your unlock token or Super CID, you can re-unlocked your bootloader once you are done and flash SuperSU to get root back. Or just flash a pre-rooted stock ROM.
3. Not sure. Make sure to fully read the post. I have never run an RUU for a phone with an RUU from a different carrier. Again, make sure you read about that one.
4. You just don't want to run the 2.20 RUU for AT&T. It will make it so you can not flash radios at all and you must flash boot.img from adb or from Android terminal emulator. It is just the 2.20 RUU that will do this. A custom ROM will not, so no need to worry.
5. It will not disable LTE, but if you don't have an LTE APN in your phone it shouldn't be looking for LTE and you can also turn off the LTE radios on any non-AT&T ROM.
My recommendation after all of your questions would be to flash a pre-rooted stock ROM or a cleaned up debranded ROM (like Clean Rom, but there are more out there). Change the APN to what ever country you are in and do the *#*#4636#*#* thing to turn off your LTE radio. Again, the *#*#4634#*#* to turn off the radio will not work on a stock AT&T ROM.

Thank you, Butters. Still I've got one more question - added in the first post.

linhldz said:
Thank you, Butters. Still I've got one more question - added in the first post.
Click to expand...
Click to collapse
If you are flashing a custom ROM, you do not have to worry about your HBOOT being changed. It doesn't matter what the custom ROM is based on. You only have to worry about that with running an RUU (which is from HTC for a specific carrier).
If you have 1.85 on your phone, just keep a 1.85 RUU on your computer and flash away any ROM you want. If something gets messed up and you need to RUU, you'll always have that 1.85 RUU with the old hboot.
Running the 2.20 RUU, you will lose all ability to flash any radios, so you will be stuck with the AT&T 2.20 radio. Being that you are overseas, I would not recommend this because it may not (probably isn't) the best radio for your use case.

If you want a stock ROM, there are pre-rooted versions posted in Development that are flashable from TWRP. Easier then relocking the bootloader and running the RUU, and no threat of hboot changes (or having to research what was changed in the hboot).
Or just install a custom ROM. They are often based on recent firmware versions, but already de-bloated, and with awesome customizations added.
After all, if you want to run a stock RUU, why did you unlock the bootloader in the first place?

Thank guys, really appreciate. Just flashed CR5 with confidence, so far so good.
Early assessment: Quite smooth, the LTE problem with AT&T stock rom has disappeared, battery life improves greatly.

[Q] RUU not working to update RADIO from new HBOOT

Hello,
I'm running Trickdroid 8.1.0 with HBOOT-1.14, RADIO-1.06s, unlocked bootloader and SuperCID. Original my device is WWE Dutch.
I figured out there would basically two ways to update my radio to the newest 1.08ts from TMOUS 2.35.531 RUU.
1) I just run 'fastboot flash radio radio.img', but no that's not working with hboot-1.14 cause we get the 'signature fail error'
2) I flash stock recovery and then relock my bootloader (that steps are fine) and then run RUU_Ville_U_TMOUS_1.84.531.2 and then update to OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.7 to obtain the new RADIO-1.08ts. But no even that's not working, I get error 155 at the RUU cause I should need the right RUU. I thought I should be able to use TMOUS RUU cause I'm SuperCID but it's just not working.
So, it looks like there is absolute no way to update my radio to 1.08ts right?

Inferi0r said:
Hello,
I'm running Trickdroid 8.1.0 with HBOOT-1.14, RADIO-1.06s, unlocked bootloader and SuperCID. Original my device is WWE Dutch.
I figured out there would basically two ways to update my radio to the newest 1.08ts from TMOUS 2.35.531 RUU.
1) I just run 'fastboot flash radio radio.img', but no that's not working with hboot-1.14 cause we get the 'signature fail error'
2) I flash stock recovery and then relock my bootloader (that steps are fine) and then run RUU_Ville_U_TMOUS_1.84.531.2 and then update to OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.7 to obtain the new RADIO-1.08ts. But no even that's not working, I get error 155 at the RUU cause I should need the right RUU. I thought I should be able to use TMOUS RUU cause I'm SuperCID but it's just not working.
So, it looks like there is absolute no way to update my radio to 1.08ts right?
Click to expand...
Click to collapse
The new Jelly Bean firmware will no doubt come with a new radio. Also I don't recommend using a different branded carrier's radio.
Sent from my locked, tampered ville

radio
uunderstanding 65 said:
The new Jelly Bean firmware will no t come with a new radio. Also I don't recommend using a different branded carrier's radio.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
Hi, is my understanding correct that jb will improve the radio on my HTC one s so I should get better reception!?

Probably he means that we have to wait for the HTC Europa JB RUU, which will have the latest radio with all improvements by now.
So far I know there is no radio branding. Everyone is talking about it but I still almost sure there is no TMOUS or Europe specific Radio. Cause it wasnt there for my previous htc devices too
Sent from my HTC One S using xda premium

Inferi0r said:
Probably he means that we have to wait for the HTC Europa JB RUU, which will have the latest radio with all improvements by now.
So far I know there is no radio branding. Everyone is talking about it but I still almost sure there is no TMOUS or Europe specific Radio. Cause it wasnt there for my previous htc devices too
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Why do some RUUs have different radios than others? T-Mobile US is definitely different, they contain tweaks as far as I know that optimizes it for their frequencies etc.

[Q] RUU error 131

I want to send back my phone to htc because my earpiece is not working correclty. I rooted my phone with AlpharevX method. I wanted to go back to S-ON and stock rom so i dont void my warranty. I flashed 0.98 bootloader and the i run RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed but it stoped updating the phone and gave me ERROR 131. It changed bootloader and radio but my phone has no rom inside. What should i do now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wooow there is a big mess here!
First your phone is branded. You have to use the proper RUU. European won't do. Not true
Second you have used a leaked RUU firmware, posted by mdeejay so you should have used misc_version.
Third now you stuck without root so you have to use htcdev.com
Sent from my HTC Desire S

I thought my phone was not branded.... I should have checked that beforehand. I called HTC and they have the ruu for my phone but they wont give it to me... I'll try to find it elsewhere... not even htc has it on their site. If i get the old RUU will it flash the old bootloader and old radio? or im stuck on the new ones?

Sorry
I have checked and your CID is included in the European RUU. But still you have used the wrong RUU because 2.10.401.9 contains only the CID for Russia. The last GB RUU for the rest of the European region is 2.10.401.8
Anyway now even if you can get back the old 0.98 hboot you cannot use Revolutionary, because you need USB Debugging and an booted OS for it. With the Stock recovery you cannot use the misc_version. I am afraid the only way is htcdev.com flash a custom recovery, use the misc_version, relock the bootloader then go back to stock with a proper RUU. I hope they will acknowledge that your problem is hardware related and has nothing to do with the unlocked bootloader. But you can avoid that if you use older RUU (1.28 or 1.47) there is no Locked/Relocked line there

I run RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068 everything went ok, phone booted. Ready to ship to HTC for repair! Thanks amidabuddha

ignited said:
i checked the EU ICS update and has my cid in there.... i flashed it and it updated ok... now it is booting....
Click to expand...
Click to collapse
You was fast
This is an option too.
There was a way with an OTA but now it is too late for that. The ICS RUU should keep the warranty on the hardware and I hope they will acnowledge it.

amidabuddha said:
You was fast
This is an option too.
There was a way with an OTA but now it is too late for that. The ICS RUU should keep the warranty on the hardware and I hope they will acnowledge it.
Click to expand...
Click to collapse
The ICS RUU is not official either?

ignited said:
The ICS RUU is not official either?
Click to expand...
Click to collapse
Well it is semi-official, so to say But should keep the warranty on the hardware.
Also the OTA way that I was thinking about has a 50 % chance to work, because it includes a modification of a signed by HTC zip.
So in any case the ICS RUU is the better option compared to htcdev.com unlock in terms of warranty. And the easier as well.
Good luck with the repair and sorry if I confused you somehow with my posts.

HTC INCREDIBLE S 710e
I follow the instructions to downgrade and s off my htc incredible s710e from this page.
http://forum.xda-developers.com/showthread.php?t=2118187
everything going quite right but during RUU installing i got an error message which says that this RUU is not suitable for you please select suitable RUU for your handset.
Igot RUU from this page.
http://d-h.st/vgw
now i want a Suitable RUU for my HTC.
HTC INCREDIBLE S 710e
HBOOT-2.02.002
RADIO-3831.18.00.11_M
eMMC_boot
May 22 2012
Android 4.0.4 (Ice Cream Sandwich)
Full HTC Sense 3.6 Interface
Multi-language (WWE)
softwre # 4.10.707.1
serial # ht23xtd11136
IMEI # 359836048384758

Wrong forum.This is Desire S.And delete serial and IMEI

Questions about the arabic version of One XL

Hi guys,
I have One XL Arabic version, Model number is "HTC EVA_UTL", CID is HTC__J15.
I'm on the latest official firmware 4.1.1, software number "1.01.401.03", build number "1.01.401.03 CL141628 release-keys".
HBoot is "2.10.0000".
Here is a picture of my HBoot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was searching the development section here, but I didn't find any thing related to my HBoot.
Can I use the Asian or the U.S. variants ROMs for this one?
Thanks,

Halim2k said:
Hi guys,
I have One XL Arabic version, Model number is "HTC EVA_UTL", CID is HTC__J15.
I'm on the latest official firmware 4.1.1, software number "1.01.401.03", build number "1.01.401.03 CL141628 release-keys".
HBoot is "2.10.0000".
I was searching the development section here, but I didn't find any thing related to my HBoot.
Can I use the Asian or the U.S. variants ROMs for this one?
Thanks,
Click to expand...
Click to collapse
That's tough to answer without testing. It "SHOULD" be safe but without testing there's no way to know for sure.. the drivers that come with your hboot may or may not mesh well with the roms since they are typically based off aT&T or Telus Roms.

Strange... Two posts about this phone within 24 hours. As exad said, it SHOULD work, but nothing is guaranteed. If you would be our guinea pig, then it would help out numerous other people. If you don't feel comfortable doing that, then it's totally understandable.

Yrah and that makes it three posts within a week. I wonder if it's just been released recently.
Sent from my Evita
---------- Post added at 02:55 AM ---------- Previous post was at 02:51 AM ----------
Here's that other thread I was talking about before, this guy says he was able to flash our ROMs onto his Evita UTL.
http://forum.xda-developers.com/showthread.php?p=43237946
Sent from my Evita

It's OK to make it as guinea pig for others, but my only concern is that I can't find any RUU for it, as a last defense line
I'll try to search again.

Halim2k said:
It's OK to make it as guinea pig for others, but my only concern is that I can't find any RUU for it, as a last defense line
I'll try to search again.
Click to expand...
Click to collapse
For the 3.18 software on our phones, it bricks if you RUU while S-ON with 11111111 or 22222222 as the CID so just be mindful of this as i imagine the latest RUU for your device, if you find one, will probably behave similarly.

Just out of interest, I had a look around. On the RUU collection thread there is a HTC GCC (Gulf Cooperation Council) RUU section which seems to fit your device with a CID of HTC__J15.
Please listen to Exad and be careful, because running an RUU with the wrong setup on your phone can definitely brick it.
EDIT: it looks like the RUU listed for your phone on the link above is lower than your current firmware configuration. Interestingly enough though, it seems to share the 1.14 hboot that our device had, which is positive.
Sent from my Evita

Thanks all for the advice.
I'll unlock the bootloader, install a recovery, nand backup, then I'll try revone S-Off.
I have an old ICS RUU, but sure it's useless without S-Off.

Halim2k said:
Thanks all for the advice.
I'll unlock the bootloader, install a recovery, nand backup, then I'll try revone S-Off.
I have an old ICS RUU, but sure it's useless without S-Off.
Click to expand...
Click to collapse
Correct! Once you're S-OFF you shouldn't have any problems RUUing at all. If you don't mind, I'd love if you update this post regarding stability of our Roms on your phone after you've had a chance to try one for a couple days.

Sure, I'll update the post tomorrow.

What's revone s-off? There's only one working s-off method for the XL and it's called Facepalm, it can be found here.
Sent from my Evita

Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Now I unlocked using HTCdev, installed Viper XL, as expected got a bootloop.
Then extracted boot.img from ROM zip and "fastboot flash boot boot.img".
Now every thing is working fine, I didn't check LTE connectivity yet, as my SIM is only 3G, I'll check it soon.
Every thing else is working fine.
There is no way to get S-OFF or to change CID as I tried every single method for One XL with no success.
Also I could not find any new RUU for the phone.
Thanks for the help guys, any questions are welcomed.

Halim2k said:
Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Now I unlocked using HTCdev, installed Viper XL, as expected got a bootloop.
Then extracted boot.img from ROM zip and "fastboot flash boot boot.img".
Now every thing is working fine, I didn't check LTE connectivity yet, as my SIM is only 3G, I'll check it soon.
Every thing else is working fine.
There is no way to get S-OFF or to change CID as I tried every single method for One XL with no success.
Also I could not find any new RUU for the phone.
Thanks for the help guys, any questions are welcomed.
Click to expand...
Click to collapse
Have you tried the JET tool?.... It would be risky but SHOULD work.
That's how I did mine as AT&T superCID methods don't work for my phone.

Halim2k said:
Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Click to expand...
Click to collapse
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita

timmaaa said:
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita
Click to expand...
Click to collapse
So true! I suppose I didn't stress this enough. Especially since JET tool does purposefully brick the phone in order to write an older Hboot. Though, theoretically even if it did brick, it should not be so far as the unbrick evita thread wouldn't be able to restore it. This of course does not make it any less dangerous. Just saying.
OP does seem to be knowledgeable, which is the only reason I am pointing out these more advanced methods that may work.

I think the the codes after the codename go like this:
U - WCDMA/GSM
L - FDD-LTE
T - TD-LTE and/or TD-SCDMA
A - FDD-LTE-Advanced
W - CDMA2000
G - GSM
D - Dualsim
H - ??
All the Evita's up to now were UL's ( WCDMA/GSM + FDD-LTE ).
This Saudi Arabia Evita being a UTL should be capable of WCDMA/GSM + TD-LTE and/or TD-SCDMA + FDD-LTE.
The difference might be all software driven, but it is unlikely. Different amps, filters etc are likely in use if not more.
It is clearly running a different hboot, radio, dsp than any EVITA_UL has had.
The HTC software versioning seems to make this device not software pegged to the Evita_UL.
The Arabic RUU is not for this device, it is for a Evita_UL like all the other devices we had seen. maybe ROM's will work but great care should be taken as the radio, hboot and dsp etc are all very likely incompatible, or will break the support of the TD technologies.
The Arabic device was from the x.xx.415.x branch not x.xx.401.x.
It seems the Arabic Evita_UL has been abondoned, it never received an update to Jelly Bean. It is possible the device was never released and was reworked to add TD-LTE and later became this Evita_UTL device.
This phone should at best be regarded as a relative of the Evita_UL but not the same device.
There is no publicly available RUU that will work with this device.
Before replacing anything backups should be taken, eg of all the partitions.
No risky actions should be taken without great care.
Assume you know nothing about this device and anything you do could brick it.

exad said:
Have you tried the JET tool?.... It would be risky but SHOULD work.
That's how I did mine as AT&T superCID methods don't work for my phone.
Click to expand...
Click to collapse
I red JET tool thread, and for sure it will hard brick my phone.
timmaaa said:
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, I tried revone as I was almost 99% sure it's safe, as it's not envolving any HBoot flashing.
twistedddx said:
I think the the codes after the codename go like this:
U - WCDMA/GSM
L - FDD-LTE
T - TD-LTE and/or TD-SCDMA
A - FDD-LTE-Advanced
W - CDMA2000
G - GSM
D - Dualsim
H - ??
All the Evita's up to now were UL's ( WCDMA/GSM + FDD-LTE ).
This Saudi Arabia Evita being a UTL should be capable of WCDMA/GSM + TD-LTE and/or TD-SCDMA + FDD-LTE.
The difference might be all software driven, but it is unlikely. Different amps, filters etc are likely in use if not more.
It is clearly running a different hboot, radio, dsp than any EVITA_UL has had.
The HTC software versioning seems to make this device not software pegged to the Evita_UL.
The Arabic RUU is not for this device, it is for a Evita_UL like all the other devices we had seen. maybe ROM's will work but great care should be taken as the radio, hboot and dsp etc are all very likely incompatible, or will break the support of the TD technologies.
The Arabic device was from the x.xx.415.x branch not x.xx.401.x.
It seems the Arabic Evita_UL has been abondoned, it never received an update to Jelly Bean. It is possible the device was never released and was reworked to add TD-LTE and later became this Evita_UTL device.
This phone should at best be regarded as a relative of the Evita_UL but not the same device.
There is no publicly available RUU that will work with this device.
Before replacing anything backups should be taken, eg of all the partitions.
No risky actions should be taken without great care.
Assume you know nothing about this device and anything you do could brick it.
Click to expand...
Click to collapse
Thanks for the info.
I spent the last 2 days searching and reading about this variant, and you are right.
This one has TD-LTE support, and it is different than any other variant, and of course we can't cross flashing boot image.
That is why I think 4G LTE will not work with cooked ROMs.
Also without a proper backup, there no way to go back to stock firmware, as this firmware version which is "1.01.401.03" is the initial release.
Now my most important concern is to find stock RUU or OTA for this variant, which I really appreciate any help about it.

I would ask tour carrier about it. They should have an ruu or ota. If you can extract the radio you should be able to run our roms
Sent from my One X using xda app-developers app

Just some more random info. The source for this device and software version was released in March by HTC. HTC dont have a habit of releasing source prior to the release of the device.
When it first got released it caught my eye because of the software version not matching the existing pattern and the T in the model.
Maybe you can find someone with a bit of spare time to compare what can be found in the kernel for differences to the evita_ul.
http://dl4.htc.com/RomCode/Source_and_Binaries/evitautl-jb-crc-3.4.10-cl141628-1.zip
Also seems like a prerelease 1.00.401.01 existed.
mid is reported in other forums as PJ8350000

@guys
Need ur help in restoring my bricked phone! HTC EVA_UTL, i did was s-off and then tried to flash the "RUU_Evita_UL_Vodafone_DE_1.82.162.4_Radio_0.17a.32.09.04_T_10.85.32.16L_release_260067_signed" thru SDCARD method and when it asked me to confirm to update by pressing the volume up button, i did! and it just satrted flashing the first part and then went dead!
so i would like to know if there's a way to fix it by copying it from other same model phone or any thing?
pls inform?
WBR
ReyTech.