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] dead screen. need assurance about unrooting

First off, thanks for all the help I've had from the xda community over the past few months. I've only just signed up, but I've been an avid noob learner thanks to your guides and various threads. Much appreciated.
Now my question: My Sensation is rooted, currently with Revolution HD (6.?.?) installed and everything has been running smoothly since I first flashed a custom ROM a few months back, but last night it powered down after the battery died and now the screen won't power up. It seems to be charging, it vibrates when I power the phone, and adb recognizes it when I search for connected devices, but the screen is flat out dead. Not a blank, black screen, just dead. No power to it.
Obviously I'd like to send it in for repair, so I need to unroot while making sure the stock recovery has been installed in place of CWM and that it is S-on.
I found a guide to unrooting with adb which seems straightforward enough, but how can I be sure everything has worked without the benefit of seeing the phone's screen?
Thanks in advance
-Bizwax

If your screen ain't working I guess you're SOL

So if I attempt to unroot with adb, can I not then use it (or another app) to confirm the status of my phone's firmware, recovery and s-on/off before I decide whether to send it for repair or not?

I don't know. I have heard of a few people sending in phones that wont turn on and HTC fixes or replaces them anyways. I guess they change out the main board. Wait a while longer and see what other people say.

That's the problem, the phone does seem to boot, so if they simply need to replace the screen they're going to see that it's rooted. Then they've got me over a barrel - they have my phone and would be within their rights to hold it until I pay for their repairs.

I don't know how they do it over in the UK but in the US they can't force you to pay for a repair if you don't want it. I'm pretty sure that they will tell you if there will be a charge before they do the repair. But they may do things differently over there.

hmm..the screen is completely dead and not even showing bootloader screen right
then doing un root and reverting the cid and all is little bit tough but completely possible
first i require some data
for that you need to go to bootloader
to do that
just power off the phone...remove the battery..reinsert the battery and then press power + voulme down buttons together..that should take you to bootloader screen (small vibration happens when you do that )
to verify that phone is connected to bootloader or not
connect the phone to pc ..
then in adb folder
type "adb devices" ->this should not show your device
type 'fastboot devices" -> this should show your device
once fastboot recognizes your device
type this "fastboot getvar all" and post the complete output
except IMEI and serial number (these are sensitive data )
then I'll guide you further

I'm just thinking worst case scenario. I don't know HTC's repair process, but if they check it over instead of running a full diagnostic and realise it's just the screen needs replacing, then they do that and test to see everything is working ok and that's when they spot that it's rooted, that would be a problem. They would already have done the work and I'd be obligated to pay them for that. Maybe I'm being overly cautious/paranoid, but still, if there's a way for me to unroot I'd rather go that route.
Someone on IRC pointed me towards android app VNC Server. That would give me remote access to my phone, plus a live screen capture gui to work through, so that might be a possibility. I know I can use adb to install it and I think I can use it to remotely boot apps on my phone too. I'm still looking into how I would do that though. Then the problem is that VNC requires a rooted device to work, which would probably be fine at the moment, but once I go to unroot that plan goes out the window. Unless I can find an alternative for unrooted phones.
Edit: that's right ganeshp. No screen activity whatsoever. Thanks for the advice, I'll get on that now.

Code:
C:\adb>adb devices
List of devices attached
123456789012 device
C:\adb>adb reboot-bootloader
C:\adb>fastboot devices
123456789012 fastboot
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.27.1100
INFOversion-baseband: 11.22.3504.07_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.32.401.3
INFOserialno: 123456789012
INFOimei: XXXXXXXXXXXXXX
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG58*****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4043mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.525s
I know you said to exclude the serial number as well, but 123456789012? Is that a big deal or is it just because it's flashed with a custom rom?
Volume plus power button doesn't work btw. I had to use adb. Just thought I'd add that in case. Every little helps, right?

well you are SOFF and supercid ..thats all i need..i mean you can actually RUN any RUU
but I Think you are from UK and orange network (from your profile )...so lets go for that corresponding RUU
get the ICS RUU from this thread
SHIPPED PYRAMID ROMS
i found one along the line "RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe" get that if you have normal sensation
if you got sensation XE
i cant find XE version of ORANGE RUU (the name has LE ..means an XE version) ...search the thread
otherwise get this XE version
"RUU​_Pyramid​_LE_HTC​_Europe​_1.73​.401​.4_Radio​_10.58​.9035​.0.."
then running the RUU
connect your phone to pc while in fastboot ..(just like earlier) then
run the ruu from pc
follow the onscreen instructions
this RUU ..will wipe everything and make it stock...except SOFF and supercid
once RUU run is over
we will change the cid back to normal
first get your cid from here (i think your cid is ORANG001..but confirm from the thread again)
CID LIST
once you know the cid...back to fastboot and connect it to PC
type this command
fastboot oem writecid <yourCID> (eg fastboot oem writecid ORANG001)
this will get your cid back to normal/original
now reboot normally (this is must to change CID)
using command
fastboot reboot
now the most important and careful step (this should be done last..i MEAN LAST)
back to fastboot again..and connect it to pc
now type this
fastboot oem writesecureflag 3
after this
do a reboot using fastboot reboot
thats all now you are stock

I am with Orange but my Sensation (standard not XE) was unbranded when I bought it. I take it the RUU_Pyramid_HTC_Europe_ roms are the ones I should be looking at?
The Fileserve links aren't working anymore but I found another collection of RUUs here. Is that site ok because I'm grabbing one of them now (RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe)
Oh and about the serial number, how do I get that back to what it should be? eg. SH15FG36536. I do have the CWM backup from when I first rooted if it's needed
Please excuse my noobness.

Bizwax said:
I am with Orange but my Sensation (standard not XE) was unbranded when I bought it. I take it the RUU_Pyramid_HTC_Europe_ roms are the ones I should be looking at?
The Fileserve links aren't working anymore but I found another collection of RUUs here. Is that site ok because I'm grabbing one of them now (RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe)
Oh and about the serial number, how do I get that back to what it should be? eg. SH15FG36536. I do have the CWM backup from when I first rooted if it's needed
Thx
Click to expand...
Click to collapse
RUU will take care of it..no worries..and no one check it too afaik

Kevc44485 said:
I don't know how they do it over in the UK but in the US they can't force you to pay for a repair if you don't want it. I'm pretty sure that they will tell you if there will be a charge before they do the repair. But they may do things differently over there.
Click to expand...
Click to collapse
They can never force anybody, I'm pretty sure that's illegal worldwide. Anyway, try and ask HTC how much it will be but I'm guessing a lot. I enquired how much it would my semi bricked sensation which is now perfect and it was £100.
Sent from my Sensation using XDA

sensation lover said:
They can never force anybody, I'm pretty sure that's illegal worldwide. Anyway, try and ask HTC how much it will be but I'm guessing a lot. I enquired how much it would my semi bricked sensation which is now perfect and it was £100.
Sent from my Sensation using XDA
Click to expand...
Click to collapse
They could if you gave them a phone that was supposedly under warranty and then it turns out that the warranty turns out to be void due to custom software.
Hope you get everything sorted out op
Sent from my sensational sensation 4g

Quick update; ganeshp's instructions at the bottom of page 1 of the thread helped a lot and I now have a stock Sensation with cid HTC__001 and S-on. It's booked for pickup by HTC tomorrow.
I did run into an issue after running the RUU update though. The installation completed ok but then I couldn't get the phone to show up in adb or fastboot devices. After retrying the RUU install a few times (with plenty of failed RUU install attempts and another issue where the phone wouldn't get out of recovery mode in adb) I finally got it to work and completed ganeshp's steps. All is good
I just hope the serial number thing (showing as 123456789012 in adb) doesn't come back to bite me on the backside. I found another guy on here with the same issue and apparently it was down to a corrupted pds partition.

Sorted. Got the phone back this morning, new screen and main board. Thanks lads

ganeshp said:
well you are SOFF and supercid ..thats all i need..i mean you can actually RUN any RUU
but I Think you are from UK and orange network (from your profile )...so lets go for that corresponding RUU
get the ICS RUU from this thread
SHIPPED PYRAMID ROMS
i found one along the line "RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe" get that if you have normal sensation
if you got sensation XE
i cant find XE version of ORANGE RUU (the name has LE ..means an XE version) ...search the thread
otherwise get this XE version
"RUU​_Pyramid​_LE_HTC​_Europe​_1.73​.401​.4_Radio​_10.58​.9035​.0.."
then running the RUU
connect your phone to pc while in fastboot ..(just like earlier) then
run the ruu from pc
follow the onscreen instructions
this RUU ..will wipe everything and make it stock...except SOFF and supercid
once RUU run is over
we will change the cid back to normal
first get your cid from here (i think your cid is ORANG001..but confirm from the thread again)
CID LIST
once you know the cid...back to fastboot and connect it to PC
type this command
fastboot oem writecid <yourCID> (eg fastboot oem writecid ORANG001)
this will get your cid back to normal/original
now reboot normally (this is must to change CID)
using command
fastboot reboot
now the most important and careful step (this should be done last..i MEAN LAST)
back to fastboot again..and connect it to pc
now type this
fastboot oem writesecureflag 3
after this
do a reboot using fastboot reboot
thats all now you are stock
Click to expand...
Click to collapse
Hello there, I was in a very similar position the OP was in.
My Sensations' screen was only displaying static. I left the screen on and after returning to the phone, the display was frozen. After taking the battery out and restarting it, it would only show static (when the HTC logo should appear) but the phone was functional as I could change the volume and hear sounds from the phone, but there was only static showing,
So I needed to get it repaired from HTC but the phone was rooted, S-OFF and supercid so I was very happy when I found this guide as it explained how to get back to stock when you can't see the display.
This was is how my phone was when it was S-OFF and supercid
{
"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"
}
After following the guide to get S-ON and cid back to stock (orange branded):
I installed the RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe.
I sent the phone off exactly 2 weeks ago and got the phone back today not repaired.
A letter with the phone stated the phon was BER (Beyond Econimic Repair) since the phone had "Unauthorised Engineering".
I was sure everything was back at stock so how can they say it is BER because of "Unauthorised Engineering".
Apologies for the long post but what can I do?

carlitob10 said:
Hello there, I was in a very similar position the OP was in.
My Sensations' screen was only displaying static. I left the screen on and after returning to the phone, the display was frozen. After taking the battery out and restarting it, it would only show static (when the HTC logo should appear) but the phone was functional as I could change the volume and hear sounds from the phone, but there was only static showing,
So I needed to get it repaired from HTC but the phone was rooted, S-OFF and supercid so I was very happy when I found this guide as it explained how to get back to stock when you can't see the display.
This was is how my phone was when it was S-OFF and supercid
After following the guide to get S-ON and cid back to stock (orange branded):
I installed the RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe.
I sent the phone off exactly 2 weeks ago and got the phone back today not repaired.
A letter with the phone stated the phon was BER (Beyond Econimic Repair) since the phone had "Unauthorised Engineering".
I was sure everything was back at stock so how can they say it is BER because of "Unauthorised Engineering".
Apologies for the long post but what can I do?
Click to expand...
Click to collapse
you know what mistake you did ?
you had the wrong RUU flashed
the RUU is of Europe unbranded one
you should have flashed the correct RUU
based on your CID ..you should flash this
"RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe"
see in the screenshot the version-main is 1.45.401.2
but it should be x.xx.61.x for ORANGE UK phone (so tha above one will have 1.35.61.1)
that's how they figured it out about your issue
EDIT: forgot to tell you what you should do
try revolutionary SOFF and get the above RUU and flash it
here the ruu download link
flash it again
do SON
and send it back

ganeshp said:
you know what mistake you did ?
you had the wrong RUU flashed
the RUU is of Europe unbranded one
you should have flashed the correct RUU
based on your CID ..you should flash this
"RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe"
see in the screenshot the version-main is 1.45.401.2
but it should be x.xx.61.x for ORANGE UK phone (so tha above one will have 1.35.61.1)
that's how they figured it out about your issue
EDIT: forgot to tell you what you should do
try revolutionary SOFF and get the above RUU and flash it
here the
flash it again
do SON
and send it back
Click to expand...
Click to collapse
OK thank you ganeshp, I am in fastboot at the moment and the phone is detected. I run revolutionary but its says "waiting for device" and nothing happens.
Why is revolutionary not detecting my phone?
EDIT: Nevermind, got it working

ganeshp said:
you know what mistake you did ?
you had the wrong RUU flashed
the RUU is of Europe unbranded one
you should have flashed the correct RUU
based on your CID ..you should flash this
"RUU_Pyramid_Orange_UK_1.35.61.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198549_signed.exe"
see in the screenshot the version-main is 1.45.401.2
but it should be x.xx.61.x for ORANGE UK phone (so tha above one will have 1.35.61.1)
that's how they figured it out about your issue
EDIT: forgot to tell you what you should do
try revolutionary SOFF and get the above RUU and flash it
here the
flash it again
do SON
and send it back
Click to expand...
Click to collapse
What about the bootloader? Isn't that supposed to be locked since HTC's warranty will not cover unlocked bootloader?
And how do check with adb if bootloader is locked or unlocked?
Thanks

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.

Demo htc one a9

I have a question about making a demo htc one a9 into a working normal phone.
I found this
http://forum.xda-developers.com/one-...etail-t3269515
and many other guides about how to do that.
The general problem for me is that I simply cannot access the developer options
(or to be more exact, turn them on from the right corner of the dev options menu...everything but "running services" is gray and can't be clicked).
Is there a way to turn them on so I can turn OEM uncloking on to unlock bootloader via HTC support
as it seems that it's the only option to access fastboot to install twrp and root this device etc.??
Thanks in advance.

I'm not exactly sure, but I believe the demo HTC One A9 is running a different software altogether. I think you have to run an RUU to bring it to a non demo phone, although like I said,I'm not sure, I've never done it before

I now tried installing a new RUU to the phone, but the problem is that no version seems to suit it!
I always get the fail message when trying the SD card method.
"10 RU_MODELID_FAIL modelid in android-info mismatched" (x3 times)
What does this mean? do I still have the wrong RUU? I tried many from here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344, including all the european versions I could find.
(Including the one where CID HTC__002 is shown).
EDIT:
As I can't use fastboot I tried finding out CID and MID using adb shell resulting:
CID = HTC__002
MID = just no answer here...
In the phones identity it says the Model number is same as the phones name (HTC One A9).
Phone number is unknown, IMSI is unavailable, bluetooth adress is unavailable...
Kernel version 3.10.73-perf-gb10289f
Baseband version [email protected]_29.05_F
Build number 1.10.401.7 CL635503 release-keys
Software number 1.10.401.7
Android 6.0, HTC Sense 7.0_g

Maybe a stupid question, but did you try typing 10 times on the build nr in the info and software section to get the developer option running?
Sent from my HTC One A9 using XDA-Developers mobile app
---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------
{
"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"
}
Just there where build nummer is written.
Sent from my HTC One A9 using XDA-Developers mobile app

Yes I have clicked the build number to open the developer settings tab.
As I mentioned in my first post ("to be more exact...") the problem is that I can't "turn them on".
By this I mean that when you open the developer settings tab it shows all the options there (OEM-unlock, USB-debugging etc.) grayed.
I can't click them from off to on. There is also a "switch" in the top right corner of the developers settings tab which makes you able to choose if the
settings are used or ignored (off). That is the "release" switch for all the real settings in the tab, and I can't turn it on!
Also, as I mentioned in my second post, I tried installing different RUU:s to the phone unsuccesfully
(they don't need the OEM unlock and could return the phone to a more normal state so I could access the dev. settings).
I also tried the windows.exe method instead of SD-card method, but somehow the phone got stuck in the update window
and that's where the situation is at the moment.
I'll probably wait for the battery to drain to zero and reboot the machine a couple times before charging it and hopefully I'll get out of that loading screen...
If anyone has an idea on how to get rid of the loading screen stuck, or an idea on how to make the dev. settings work/have a correct RUU for this device
based on the information provided in my second post, please post a reply!
Again, thanks for all the answers.

chargoal said:
Yes I have clicked the build number to open the developer settings tab.
As I mentioned in my first post ("to be more exact...") the problem is that I can't "turn them on".
By this I mean that when you open the developer settings tab it shows all the options there (OEM-unlock, USB-debugging etc.) grayed.
I can't click them from off to on. There is also a "switch" in the top right corner of the developers settings tab which makes you able to choose if the
settings are used or ignored (off). That is the "release" switch for all the real settings in the tab, and I can't turn it on!
Also, as I mentioned in my second post, I tried installing different RUU:s to the phone unsuccesfully
(they don't need the OEM unlock and could return the phone to a more normal state so I could access the dev. settings).
I also tried the windows.exe method instead of SD-card method, but somehow the phone got stuck in the update window
and that's where the situation is at the moment.
I'll probably wait for the battery to drain to zero and reboot the machine a couple times before charging it and hopefully I'll get out of that loading screen...
If anyone has an idea on how to get rid of the loading screen stuck, or an idea on how to make the dev. settings work/have a correct RUU for this device
based on the information provided in my second post, please post a reply!
Again, thanks for all the answers.
Click to expand...
Click to collapse
VolUp+Power will force power off.
The 1.10.401.7 RUU and above SHOULD flash. I'm not certain that this will solve your problem though, since your CID will still be the same (I'm pretty sure HTC__002 is for Euro demo devices only). I suggest using Sunshine to s-off and convert to BS_US001 (US unlocked) or HTC__001.

CSnowRules said:
VolUp+Power will force power off.
The 1.10.401.7 RUU and above SHOULD flash. I'm not certain that this will solve your problem though, since your CID will still be the same (I'm pretty sure HTC__002 is for Euro demo devices only). I suggest using Sunshine to s-off and convert to BS_US001 (US unlocked) or HTC__001.
Click to expand...
Click to collapse
Yeh I figured that forced shut down already, but thanks anyways.
Umm, do I need the chargeable/paid version of Sunshine to S-off?
I tried the free android version earlier and it didn't work on the phone (just said I should contact XDA help or something...).
I'm not familiar with this program (or with s-offing/RUU's/CID's etc. to be honest), so this is a bit of a learning process to me.
So if the CID is wrong (HTC_002, which you thought to be some kind of demo CID) how does this matter when it comes to the normal
use of the phone? Won't it be getting normal OTA updates or something?
Do I have to change it in order to make the phone work normally?
So you think that the only way to solve this mess is to purchase Sunshine in order to s-off without unlocking the bootloader
(going around the original problem with the dev. settings been locked) and to change the CID (and MID? does this matter?)?
Could the phone be turned into a "fresh" normal HTC without using any custom ROMs like cyanogenmod after this progress?
Is the Sunshine 100% reliable when it comes to s-offing this kind of phone? Wouldn't want to pay 25$ for nothing...
Sorry for the amount of questions.
Thanks for you help, it is much appreciated.

chargoal said:
Yeh I figured that forced shut down already, but thanks anyways.
Umm, do I need the chargeable/paid version of Sunshine to S-off?
I tried the free android version earlier and it didn't work on the phone (just said I should contact XDA help or something...).
I'm not familiar with this program (or with s-offing/RUU's/CID's etc. to be honest), so this is a bit of a learning process to me.
So if the CID is wrong (HTC_002, which you thought to be some kind of demo CID) how does this matter when it comes to the normal
use of the phone? Won't it be getting normal OTA updates or something?
Do I have to change it in order to make the phone work normally?
So you think that the only way to solve this mess is to purchase Sunshine in order to s-off without unlocking the bootloader
(going around the original problem with the dev. settings been locked) and to change the CID (and MID? does this matter?)?
Could the phone be turned into a "fresh" normal HTC without using any custom ROMs like cyanogenmod after this progress?
Is the Sunshine 100% reliable when it comes to s-offing this kind of phone? Wouldn't want to pay 25$ for nothing...
Sorry for the amount of questions.
Thanks for you help, it is much appreciated.
Click to expand...
Click to collapse
As far as I know, the only way to make the phone as if it were a stock retail device is by going s-off to change the CID. I haven't heard of Sunshine failing. It does checks to make sure it will work and doesn't charge you unless it will.
You can s-off, change CID, flash appropriate RUU, then s-on and have a completely stock, retail-converted device.
I wouldn't go back s-on if the phone is for your personal use.
Refer to the convert to unlocked thread.

HTC U11 Dual Sim / International Unlocked: not all features are working on T-Mobile

I have a HTC U11 Dual Sim / International Unlocked version that I was able to get while I was in Taiwan.
The CID of this phone is set to ChungHwa Telecom - the Mobile Carrier in Taiwan (CID = HTC__621 TWM-TW).
I am using the phone in the US with a T-Mobile SIM card, and generally it works ok. However, there are a few problems that i have, which I think are because the phone is not set to the correct CID.
1) If I am on a mobile data network, I cannot simultaneously make a phone call and use mobile data (browse using Chrome, use Google Maps, etc). I can browse data as soon as I end the call. This is not an issue when i am on a wifi network.
2) I cannot get T-Mobile's VoLTE function to work.
Questions: if I set the phone to Super CID, US Unlocked, or T-Mobile, will everything work correctly? Do I also have to change the MID, or can I leave this alone?
Is this the procedure that I should follow to change the CID? https://forum.xda-developers.com/u11/how-to/convert-sprint-branded-u11-to-unlocked-t3664154
Sorry, but I am somewhat of a noob when it comes to this, but I think that I have to use Sunshine to get S-OFF and then enter the command lines fastboot oem writecid BS_US001 or fastboot oem writecid 11111111
Then I have to flash the RUU to the US unlocked, but how exactly do I do this?

Supercid is no longer valid so the cid must match the firmware you're flashing. Yes you will need s-off, change cid, flash firmware, done.

Your first issue I have it too. I can't use data while on call. The data connection cuts the moment my phone starts ringing. And I don;t know what to do, but I can live with it.
For VoLTE, I think you need the T-mobile firmware.

RossTeagan said:
Your first issue I have it too. I can't use data while on call. The data connection cuts the moment my phone starts ringing. And I don;t know what to do, but I can live with it.
For VoLTE, I think you need the T-mobile firmware.
Click to expand...
Click to collapse
As far as Volte goes, if you change to us unlocked it'll work fine. I'm with mint sim that uses tmo and all works fine. And It's great being able to surf while talking.
US unlocked is the way to go imo.

Surf and talking are allowed only if data and call comes from the same Sim.
HTC U11 is not dual active

shivadow said:
Supercid is no longer valid so the cid must match the firmware you're flashing. Yes you will need s-off, change cid, flash firmware, done.
Click to expand...
Click to collapse
So, I managed to unlock the bootloader, used Sunshine to achieve S-Off, changed my CID to BS_001 (US developer). The last thing that I have been trying to do is flash the ROM to the US Unlocked ROM. I am running the installation utility and getting this error message: "Error [130]: MODEL ID ERROR. The ROM update utility cannot update your Android Phone. Please get the correct ROM Update Utility and try again."
I did notice this: the ROM that I have installed on my phone is: 2.42.709.1 (this was released for the Taiwanese version of the U11)
The most recent US unlocked ROM is: 2.42.617.1 (this is the one that I am trying to install on the phone).
Is this causing a problem?
Do I need to change the MID (model ID of the phone)...if so, how do I do this?
What do I do next?