Database Info

[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

[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

[GUIDE] How to change your CID to SuperCID 11111111 (k2u, k2ul)

SuperCID 11111111 for HTC One SV (k2u, k2ul)
As some people were asking and because of the completeness i'll post here the guide, to change your cid to supercid. This is the first step to get S-Off and it's mostly the same as at One S.
Credits and thanks to jmztaylor for guiding me through this painful session!
Notice:
You must know, that you can brick your device when you are doing something wrong! Only do this, if you know and understand what to do and how to do. Otherwise, let it be.
Ansonsten besser Finger weg!
I am not responsible if your device is bricked or damaged in any way!
Think about this twice!!!
I have tested this on k2_u, others reported success on k2_ul too.
For the other devices of One SV i don't know and don't give any guarantee that it will work.
Requirements:
You should have a working adb/fastboot environment and HTC drivers installed on PC. And you should know, how to handle adb/fastboot/dd commands.
USB-Debugging should be activated on the device.
The smartphone must be unlocked (over HTCdev.com) and must be rooted.
This will only work, if you are on ICS. With Jelly Bean hboot this will not work.
You need a Hex-Editor, i recommend HxD.
You can get your actuall cid with this fastboot cmd:
Code:
fastboot oem readcid
Result for me: HTC__102
How to:
Open cmd window where your adb is located.
There you make the following commands one after the other:
Code:
adb shell
Code:
su
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4.img
Code:
exit
Code:
exit
Code:
adb pull /sdcard/mmcblk0p4.img
Now your bootloader is extracted to SD card, then into your adb folder.
Look at the file size of mmcblk0p4.img, it MUST be the same size after changing the cid! Don't flash it back, if it isn't the same size.
Now open the mmcblk0p4.img with Hex-Editor and look, where your cid is located (on my picture it is HTC__102). Afterwards it is followed by your IMEI number.
{
"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"
}
Now you have to overwrite your cid, Not copy and paste!
That means, put the cursor before H of HTC__102 and then you have to add 8 times the number 1 so it then looks like in the next picture.
If you are doing something wrong, HxD will complain. If not, it should be ok.
Now save.
Don't forget to check the filesize!
Back to command line you have to make the following commands one after the other:
Code:
adb push mmcblk0p4.img /sdcard/mmcblk0p4MOD.img
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/mmcblk0p4MOD.img of=/dev/block/mmcblk0p4
Code:
exit
Code:
exit
Code:
adb reboot bootloader
Now you can check your new supercid with the fastboot command:
Code:
fastboot oem readcid
The result should be 11111111
Now you can go on, making your device S-Off.
Have fun!

Any chance to get super CID for all those who has JB alredy installed?? because i guess that i can´t go back to ICS , can i??
thanks

titin83 said:
Any chance to get super CID for all those who has JB alredy installed?? because i guess that i can´t go back to ICS , can i??
thanks
Click to expand...
Click to collapse
I'd also love to know the answer :good:

CID didn't changed
Hello and thanks for your time creating this guide.
I done everything exactly as you said but my CID didn't change...
My SV is K2_UL with HBOOT - 2.00
Any help?

Stallion34 said:
Hello and thanks for your time creating this guide.
I done everything exactly as you said but me cid didn't change...
My SV is K2_UL with HBOOT - 2.00
Any help?
Click to expand...
Click to collapse
Its because your on hboot 2.00. You need to S-Off your device with Moonshine and then you can change CID, if you still want.
And please, remove the quote of the first post, we have to scroll so long.

Thx for the answer...
I followed your suggestion but moonshine gives me an adb failure during the proccess...
I want to S-off my device and then try your custom JB rom...

Stallion34 said:
Thx for the answer...
I followed your suggestion but moonshine gives me an adb failure during the proccess...
I want to S-off my device and then try your custom JB rom...
Click to expand...
Click to collapse
You are already on JB, so there is no real profit for you, cause mine is not modded.
Let's talk in the Moonshine thread.

I can't post on development forums yet because I have < 10 posts
Anyway, I managed to S-OFF my device.
I disabled Root Call Blocker from running on Device boot and everything worked fine...
After S-OFF I changed successfully my CID (in case of needing it in future)
Thx again for your time.
Two last questions for you.
Is there any info from HTC about ONE SV and 4.2.2 android?
Do you know if CM or MIUI will develop firmware for ONE SV?
Thx in advance...

Stallion34 said:
I can't post on development forums yet because I have < 10 posts
Click to expand...
Click to collapse
Oh sorry, iforgot.
Anyway, I managed to S-OFF my device.
I disabled Root Call Blocker from running on Device boot and everything worked fine...
After S-OFF I changed successfully my CID (in case of needing it in future)
Click to expand...
Click to collapse
Fine.
Is there any info from HTC about ONE SV and 4.2.2 android?
Do you know if CM or MIUI develop firmware foer ONE SV?
Click to expand...
Click to collapse
CM i think yes, MIUI i don't think atm.
All info about 4.2.2 you'll find here.

Once we are S-OFF, why could be useful change our CID to 1111111?i got S-OFF whit moonshine but my hboot is still in 2.0.
Should I change it?
Thanks

titin83 said:
Once we are S-OFF, why could be useful change our CID to 1111111?i got S-OFF whit moonshine but my hboot is still in 2.0.
Should I change it?
Thanks
Click to expand...
Click to collapse
Updates! (if we will get some, lol)
A german "test" HTC One of a big internet website got the Android 4.2.2 update and they made a news article, the update is rolling out in germany. But others didn't get it.
In the end the phone had SuperCid and that was, why the phone got an update earlier than others.
Isn't that funny

FYI boost mobile keeps their CID in the same block. BUT it bricked my phone, I REPEAT, I BRICKED MY BOOST MOBILE k2_cl ONE SV, by trying to change to superCID.
I also got lucky and the nice people at radioshack gave me another @ no cost.
Just be more careful and beware Bricks can and will happen if you aren't prepared ( i.e. I was too lazy to actually use the method in this guide and used a terminal emulator on my phone) and gave myself a beautiful brick.

russellvone said:
FYI boost mobile keeps their CID in the same block. BUT it bricked my phone, I REPEAT, I BRICKED MY BOOST MOBILE ONE SV, by trying this superCID.
I also got lucky and the nice people at radioshack gave me another @ no cost.
Just be more careful and beware Bricks can and will happen if you aren't prepared ( i.e. I was too lazy to actually use the method in this guide and used a terminal emulator on my phone) and have myself a beautiful brick.
Click to expand...
Click to collapse
perhaps, you are not lucky
I had success with this way, and i'm very happy

I was just informing and sharing that I tried to change my CID with a different method than the one posted in the guide. And I failed to profit from it.

Yup, thats why i stated that this is very risky and for k2u/k2ul! The first one who tried the guide in german board also bricked his device by using a different hex-editor. He got a new one for free too.
But it is damn risky, everybody should know it, when trying.
I followed the guide exactly and got 2 One SV set to SuperCID.

You warned me... Lol should have listened :thumbup:

Lets say, its good, when you can return it for warranty.
There is no need to say, that you've bricked it yourself. You can say it doesn't start from one minute to the next...

Hello ! I did the precedure but there was img size and i didnt change it ... Can i lock bootloader and to expect the update if i relock my bootloader ? Thanks for some answear ! Btw i got custom recovery installed if this is importent

You can always relock your bootloader with cmd:
Code:
fastboot oem lock
But with custom recovery the OTA update will for sure fail!

ah my luck ... :/ I already done the steps from here andonce i was with success now i got error : device not found ... cant found where is my mistake :/ S-OFF and all , is like some circle :/ Can anybody help me ?

Steps to install custom rom

hi there..
i'm new on this section..cause i just bought the device.. anyway..
i read almost most important topics about s-off and super cid and custom recovery.. but i can not be 100% sure that i can do this alone
HTC HD2 is my first android device and i almost aware of how the things work to have a stock rom on y device..
but because of my device has not any warranty so i need to be careful not to brick my phone..
so i want to ask you guys help me step by step to do this right..
i think first i need to s-off my phone / read about this on some persian forums / to do this i have to get the unlock code from HTCDev ..right?
i know the steps..
next i need to install custom recovery which TWRP 2.6.3.0 is better than other version..right?
then i move the downloaded rom to my phone and from the recovery i install it.. right?
that was the final step.. ok?
so what about super cid.. how can i do this? is it necessary or what?
how can i back to stock rom/?
and what is the best rom for battery saveing which has sence 5?
thanks..

If you have the HD2 you're in the wrong forum, this is the One XL forum. You need to find the correct forum and ask there as each device has different methods to unlocking and rooting.
Sent from my Evita

timmaaa said:
If you have the HD2 you're in the wrong forum, this is the One XL forum. You need to find the correct forum and ask there as each device has different methods to unlocking and rooting.
Sent from my Evita
Click to expand...
Click to collapse
thanks for noticing ,,, BUT ...
{
"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"
}

Firstable...wrong forum but since u new...is ok.....u need to start somewhere first.... Basically installing custom rom is always same process but different phone different method.....like timmaaa said on previous post.
1. U need to get root....to get superuser
2. Install recovery
3. U need to unlock your bootloader from Htc.Dev and choose your device
4. SuperCID .....
5. S-OFF
6.Download Custom ROM of your choice
7.Flash ROM from recovery....
8.Enjoy your custom ROM
But remember different device .....different method to root...etc
Swyped From BlueICESense_JBE

first of all thanks for help..
guys.. i bought HTC One XL.. belongs to no carrier.. i'm in middle east.. i do not understand what are saying about different device..
you mean every one xl with different carrier has its own method to root or s-off or etc.. interesting..
so now you know about my phone..
by the way i know the steps.. how can i do them/
i mean first i should unlock my bootloader to root my phone or install recovery..right?
but the order of the steps ted77usa said is different and i am totally confused.. you know what i mean?
what is the difference between s-off and unlock the bootloader?
is superCID necessary and if yes how do i do this?
these are my problems...

jabi_james said:
first of all thanks for help..
guys.. i bought HTC One XL.. belongs to no carrier.. i'm in middle east.. i do not understand what are saying about different device..
you mean every one xl with different carrier has its own method to root or s-off or etc.. interesting..
so now you know about my phone..
by the way i know the steps.. how can i do them/
i mean first i should unlock my bootloader to root my phone or install recovery..right?
but the order of the steps ted77usa said is different and i am totally confused.. you know what i mean?
what is the difference between s-off and unlock the bootloader?
is superCID necessary and if yes how do i do this?
these are my problems...
Click to expand...
Click to collapse
Well at first u said ur phone/device are HTC HD 2 ....now u said Htc one Xl.....htc one xl mean from att ...if u do have htc one xl .....u are on the right forum and right device......all the step are connected.....u need to root ur device first so u can install recovery Twrp is recommended for our device.....coz to install recovery required superuser permission......U know what.... first thing first......power off your phone and then hold power+volume down combo button.....this would bring u to your bootloader and tell us what kinda hboot that u have? Either s-off or s-on.....locked or unlocked.....and what version of your Hboot so we can go from there......because diferent hboot is diferent method and steps......If u have adb/fastboot.exe u can plug your device to Pc ...and enter command from where u save adb/fastboot file......code are : adb reboot bootloader this would reboot your phone and bring you to your bootloader......And knowledge for adb/fastboot is required in order for u to mod your device......if your bootloader unlockEd.....most likely u have supercid....coz during process of unlocking bootloader u chance your device ID for example At&t is CWS__001 and u change it to 11111111 ( supercid ) but diferent carier is diferent thats what i mean and YES supercid is required for S-OFF......And u said u bought Htc one X with no carrier ....u might have international htc one X......not htc one xl that's different device
Swyped From BlueICESense_JBE

jabi_james said:
first of all thanks for help..
guys.. i bought HTC One XL.. belongs to no carrier.. i'm in middle east.. i do not understand what are saying about different device..
you mean every one xl with different carrier has its own method to root or s-off or etc.. interesting..
so now you know about my phone..
by the way i know the steps.. how can i do them/
i mean first i should unlock my bootloader to root my phone or install recovery..right?
but the order of the steps ted77usa said is different and i am totally confused.. you know what i mean?
what is the difference between s-off and unlock the bootloader?
is superCID necessary and if yes how do i do this?
these are my problems...
Click to expand...
Click to collapse
The problem was that in the first post you only mentioned the HD2, hence the confusion. To help you properly I'm gonna need to see your bootloader details please. If you have the middle eastern model this might be tricky.
Sent from my Evita
---------- Post added at 11:02 AM ---------- Previous post was at 11:00 AM ----------
ted77usa said:
Well at first u said ur phone/device are HTC HD 2 ....now u said Htc one Xl.....htc one xl mean from att ...if u do have htc one xl .....u are on the right forum and right device......all the step are connected.....u need to root ur device first so u can install recovery Twrp is recommended for our device.....coz to install recovery required superuser permission......U know what.... first thing first......power off your phone and then hold power+volume down combo button.....this would bring u to your bootloader and tell us what kinda hboot that u have? Either s-off or s-on.....locked or unlocked.....and what version of your Hboot so we can go from there......because diferent hboot is diferent method and steps......If u have adb/fastboot.exe u can plug your device to Pc ...and enter command from where u save adb/fastboot file......code are : adb reboot bootloader this would reboot your phone and bring you to your bootloader......And knowledge for adb/fastboot is required in order for u to mod your device......if your bootloader unlockEd.....most likely u have supercid....coz during process of unlocking bootloader u chance your device ID for example At&t is CWS__001 and u change it to 11111111 ( supercid ) but diferent carier is diferent thats what i mean and YES supercid is required for S-OFF......And u said u bought Htc one X with no carrier ....u might have international htc one X......not htc one xl that's different device
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Hang on, that's not exactly right. Not all Evitas are from at&t, they are available in several countries, from several carriers, branded and unbranded, and there is also a middle eastern model which is a bit different. We need to establish which model he has first.
Sent from my Evita

ted77usa said:
Well at first u said ur phone/device are HTC HD 2 ....now u said Htc one Xl.....htc one xl mean from att ...if u do have htc one xl .....u are on the right forum and right device......all the step are connected.....u need to root ur device first so u can install recovery Twrp is recommended for our device.....coz to install recovery required superuser permission......U know what.... first thing first......power off your phone and then hold power+volume down combo button.....this would bring u to your bootloader and tell us what kinda hboot that u have? Either s-off or s-on.....locked or unlocked.....and what version of your Hboot so we can go from there......because diferent hboot is diferent method and steps......If u have adb/fastboot.exe u can plug your device to Pc ...and enter command from where u save adb/fastboot file......code are : adb reboot bootloader this would reboot your phone and bring you to your bootloader......And knowledge for adb/fastboot is required in order for u to mod your device......if your bootloader unlockEd.....most likely u have supercid....coz during process of unlocking bootloader u chance your device ID for example At&t is CWS__001 and u change it to 11111111 ( supercid ) but diferent carier is diferent thats what i mean and YES supercid is required for S-OFF......And u said u bought Htc one X with no carrier ....u might have international htc one X......not htc one xl that's different device
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Hey Ted, sorry to say but there are multiple things wrong with this post. Maybe just hold back on giving advice until you're well versed with this device. Giving wrong advice can lead to someone bricking their phone and nobody wants to be responsible for that.
u need to root ur device first so u can install recovery Twrp is recommended for our device.....coz to install recovery required superuser permission
Click to expand...
Click to collapse
There is no superuser permission required to install a custom recovery, it's actually the other way around: custom recovery is required to install superuser. What is required for a custom recovery though is an unlocked bootloader.
There is quite a bit of confusion over what rooting actually is, all it does is give you access to the root directory on the device, like having administrative privileges on Windows. It actually has nothing to do with the ability to flash custom ROMs, you need the unlocked bootloader and custom recovery to flash custom ROMs. A user can actually use a custom ROM perfectly well without ever needing to have root.
if your bootloader unlockEd.....most likely u have supercid....coz during process of unlocking bootloader u chance your device ID for example At&t is CWS__001 and u change it to 11111111
Click to expand...
Click to collapse
It isn't necessarily likely that a user has SuperCID if they have an unlocked bootloader, this is only true for at&t phones. All other Evitas are able to unlock the bootloader at htcdev without SuperCID. At&t phones need SuperCID first because the at&t CID is blocked at htcdev. Quite often these non-at&t phones (of which there are many) get SuperCID after unlocking the bootloader and attaining root.
And u said u bought Htc one X with no carrier ....u might have international htc one X......not htc one xl that's different device
Click to expand...
Click to collapse
Like I said in a previous post, this isn't true. At&t only makes up a percentage of all Evitas in the world. There are Evitas available in pretty much every country, and on various carriers (and unbranded) like Rogers, Telus, O2, T-Mobile, Telstra to name just a few. You can buy the One XL outright online from many websites, and these are usually the Hong Kong model, this is how I bought mine. So, to assume that a non-at&t One XL is the international One X isn't correct.
Now, while all of these Evitas are the same (apart from the availability of a 32gb model in Australia and Europe, the only difference being the storage capacity), there is a middle eastern variant of the Evita which is not like all the others. It has different hboot versions and very little is known about it, like whether all of our software is compatible or not. It's possible that it is but I've only seen three of four users with this device and I'm not comfortable advising anyone that it is. The few users that I've seen with this phone haven't reported back as to whether they've tried the software, and if so whether it worked or not.
Anyway, I just wanted to clear those things up for you, as I said it's very dangerous to give advice unless you're absolutely certain of what you're taking about. I hope this has helped somewhat.
Sent from my Evita

Well explained......:thumbup::thumbup: and sorry for what I posted.....and hope this would clear the confusion I made....... learned something new everyday.....:thumbup:
Swyped From BlueICESense_JBE

It's all part of the learning process.
Sent from my Evita

hey guys.. appreciate you for being patient..
here is my phone's HBoot information.. hope i can figure it out with your help..
what else do you need?

Ok, thanks for posting that. Please read this entire post before doing anything, it's extremely important. Your first step is to unlock your bootloader at htcdev (this isn't s-off as you previously posted though, s-off is something different). Your next step is to install TWRP recovery (I've seen people having problems with 2.6.3, so maybe stick to 2.6), but this is where it gets a little tricky, I'll tell you why.
You have the middle eastern variant of the HTC One XL, I'm able to identify that by the 2.10 hboot, and by the codename which is EVITA_UTL, all other One XL's codename is just EVITA.
The problem with this is that we know very little about your variant, I've only seen a couple, so we're not absolutely sure if the software is compatible. The only way you're going to know for sure whether the software (TWRP recovery, ROMs, radios, kernels) is compatible or not is to try to flash it. If it works, that's great and we'll all know that it's safe to use the software, and you can enjoy some custom ROMs. But, if it doesn't work, there's a high chance you could brick your phone.
So, as you can tell this is a very risky situation for you. It's entirely up to you whether you try flashing the software or not, but I thought you should be fully aware of the risk involved. Either way, please do let us know what you decide to do. If you decide to go ahead it'll provide excellent information for other guys like you with this variant of our device.
Sent from my Evita

hey there...
so these are my whole phone information
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main: 1.01.401.03
version-misc: PVT SHIP S-ON
serialno: HT2CTW305376
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 4024mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
i unlocked my bootloader few minutes ago.. but on thing.. where can i find the stock recovery image and stock RUU rom ? if anythings go wrong i would be able to go back to stock..

That's the problem, I don't know of an available RUU for your device, so I don't know if there's a stock recovery available. Maybe your carrier can provide you with that though.
I do have some good news for you though, I vaguely remembered another guy who has your device flashing one of our ROMs so I did some looking around. I found this thread. If you have a read you'll see he successfully flashed one of our ROMs and it worked fine. Please read this post in particular though, it states that you should not use hboot or radio from our device on yours, and also you will not have LTE support.
Sent from my Evita
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
PS. You really should remove your IMEI number from that post above, never post your IMEI publicly.
Sent from my Evita

Ok, I think I've worked out how to backup your stock recovery. What you want to do is download TWRP 2.6 and put it in your fastboot folder. Now you connect your phone and issue this command:
Code:
fastboot boot recovery "recovery filename.img"
(The exact recovery filename, minus the talking marks)
This will boot your phone into TWRP recovery while it's still stored on your pc without having to overwrite the stock recovery on your phone. Basically it's running an emulated recovery, and the next time to reboot it'll be gone and your stock recovery will remain on your phone.
Now, while you're in TWRP you can either install superuser binaries or a custom pre-rooted ROM. This will give you root, once you've booted into the rooted ROM you can use an app called Flashify to backup your stock recovery.
Once you've confirmed that your recovery backup has worked (using a file explorer) you're free to permanently flash TWRP recovery onto your device.
Sent from my Evita

thanks man..
you mean i can flash for example viper Xl with emulated TWRP when stock recovery still installed on my phone.. wow...
and i didn't get the last part.. how can i confirmed with file explorer that my stock recovery which has been backed up works fine ?

and one thing..
while i'm restoring the original rom my recovery would be TWRP.. well ,,so if there's an original update exist my recovery must be stock to get the update.
it's possible to flash the stock recovery after restoring the original rom without damaging to it? you know what i mean?

jabi_james said:
thanks man..
you mean i can flash for example viper Xl with emulated TWRP when stock recovery still installed on my phone.. wow...
and i didn't get the last part.. how can i confirmed with file explorer that my stock recovery which has been backed up works fine ?
Click to expand...
Click to collapse
Yeah that's exactly what I mean, it's pretty cool actually. Before flashing Viper you should use the backup tool in TWRP to backup system, data, and boot and then you'll have a backup of your stock ROM.
What I meant in the last part was you should install something like ES File Explorer from the Play Store. That way after you've backed up your stock recovery you can confirm that it worked by navigating to /flashify-backup/recovery using the file explorer to make sure the recovery image is there.
I'm about to attach a couple of screenshots for your reference, I'll have them uploaded in a couple of minutes.
Sent from my Evita

problem..
my recovery name is (openrecovery-twrp-2.6.3.0-evita)
so i write in cmd (fastboot boot recovery openrecovery-twrp-2.6.3.0-evita.img)
but it says (can not load recovery)

oh.. i think i destroy my phone .. a message appears at the top of the bootloader and says : (Tampered)
i write this command in cmd [fastboot boot "recovery filename.img"]
what did i do...

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.