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
Related
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
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
chuaniyang said:
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
Click to expand...
Click to collapse
Well it's still gonna show relocked if that's what your talking about bcuz you unlocked it then relocked so it isn't gonna show tampered with unlocked at the bottom that's only for the first time you unlock it that it says tampered with unlocked at the bottom, but if you unlock it again it's just gonna say relocked not unlocked. Hopefully this answers your question.
Sent from my samsung galaxy player
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
chuaniyang said:
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
Click to expand...
Click to collapse
Yea that is strange but I don't think it would be considered a problem unless you have the phone stuck in Bootloop or something strange is going on with the phone like apps.not working or battery draining fast. I can see what your worried about and it is strange but I wouldn't worry too much about it but you should look up somewhere in the forums about that but I wouldn't know much about the international version I'm on the US version. Good luck with your problem
Sent from my samsung galaxy player
I checked this thread
http://forum.xda-developers.com/showthread.php?t=1671643
seems I need to wait someone can S-OFF this device
superCID can install any RUU, but can't unlock, root, install custom ROM without S-OFF
I've managed to change my cid and install a new Rom then unlock it and root so it's possible
Sent from my HTC One S using Tapatalk 2
the other reason maybe user just can unlock/relock limited times. ?
does any one change CID and unlock/relock over 3 times ?
I've relocked about 4 time's now changed cid once
Sent from my HTC One S using Tapatalk 2
My default cid is HTC_203, i changed to HTC__102, HTC__001 and 11111111.
Everytime cid changed, I will lock/unlock again. When changed to 11111111, I can't unlock anymore.
Sent from my HTC VLE_U using xda app-developers app
Mate, the CID is in the partition that gets summarized together with the other partitions when calculating the Unlock Token.
So, if you change this or any other relevant partition by for example changing the CID, you will invalidate your old unlock token.
After changing CID, please re-lock bootloader, then go "fastboot oem get_identifier_token" and go to HTC-Dev and unlock again.
After that, you can proceed with everything else as usual.
If you cannot unlock with CID 11111111 this is NOT normal. Everyone else can.
So either you did something wrong in the above process or you somehow half-bricked your phone.
Yes, everytime I changed cid, I got a new unlock code. if not, fastboot will give me error message during unlock process.
I think my situation is not normal, and I'm trying to find out why then fix it. Now, I still can install any RUU , if they have the same HBOOT version.
Sent from my HTC VLE_U using xda app-developers app
I'd guess it's a half brick because if you can't unlock something is wrong. There is no unlock counter because no-one has had it yet. I've unlocked about four or five times now too and don't have that problem. You should consider sending it in for repair. As long as there's no S-OFF you'll have no chance to force an unlock I guess. If the security is as complex as on the HOX, it's likely the situation couldn't even be resolved by a jtag programmer or such.
sent from the tip of my finger
Thanks, no one have the same question as me. I will try to call HTC service.
CID 11111111 Issue
Hello there,
I want to install an older RUU (actually installed is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed )
my intention is to downgrade the Basbeand Version with this Procedure to get rid of this "HomeButton-Jumparound-Whatever" Issue which occures when i am in GSM (2G) Mode.
when i get this phone brandnew there was no Problem, just after updating to 1.78 this ****** began.
When i changed my CID from HTC__102 to 11111111 the first time everything went fine and i was able to install every RUU
Now i tried to change my Radio to an older Version by install an older RUU, but it won't work no more, i allways get an Error 140 or 131.
if there is another method to change the radio version, I'd appreciate any council
relock Bootloader, turn off virus scanners, run ruu as admistrator, I've done of course
I would be grateful for any help
ERROR 140 : bootloader error
ERROR 131 : cid error
are you install T-MOBILE 1.84 RUU ?
this will chane HBOOT version from 1.08 to 1.09
if you can unlock, try to find some way change your HBOOT version back to 1.08.
then you can insall RUU_Ville_U_HTC_Europe_1.78.401.2.
RUU_Ville_U_HTC_Europe_1.78.401.2 can be installed only with the other it does not work
i've got HBOOT 1.13.000 (shown in bootloader)
i just want to downgrade the Radio..
edit: when try to install RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed
or
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed
i get Error 155
we have some thing different. but you are lucky then me. I just can install T-MOBILE 1.84 RUU, if I try to install another version. always got HBOOT version error
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-main: 1.84.531.2
(bootloader) commitno-bootloader: e964c535
The HTC srevice center(tw) call back. they say they find some motherboard error on my device.
I don't think change cid and unlock will cause it happen.
Hello everyone.
I am new to this part of the forum for i just received a somewhat non working AT&T HTC ONE XL from a friend.
I presume he did not read much into his issue at the time and messed up this phone one way or the other.
Basically the phone works, just not as a phone.
So i will take my time to explain the whole situation with as much detail as possible.
I am personally familiar with rooting, setting up recovery and installing custom roms on android phones (just not on this model yet).
The phone details in its current state are:
- android version 4.0.4
- htc sense version 4.0
- software number cleanrom 4.5 beta2
- htc extension version htcextension_403_1_ga_20
- kernel 3.0.8-01564-gdc95f45
- baseband 0.16.32.09.01_3_10.79.32.08L
As soon as i received the phone, i contacted at&t to ask for an unlocking code, they gladly oblige.
I insert the new SIM card (non AT&T) and the phone asks me to insert the code. After correctly inserting it, the phone accepts the code and proceeds to reboot. After the reboot i get the phone locked screen again and asks me for the code one more time.
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
So at this point i am open for ideas.
I'm positive the issue is not very hard to solve but i also know that i am missing the original recovery. I can only guess no official updates were installed so the phone was running the original 4.0.4 version.
Meanwhile i will be scouting this forum on how this phone exactly works for i understood that there were two forms of recoveries for it (one full and one partial).
I still don't know the recovery version, if it's good, how to access it (different combinations of volume and power pressing didn't work for me).
Finally your opinion on how to make the phone unlocking code work, as in would i need to go back to official, or would a custom different rom work as a solution.
Wish you guys a good day and awaiting your feedback.
Cheers.
Need more info. Boot into bootloader by holding down both the volume down rocker and the power button. After the power button is held for a few seconds, you should see the capacitive buttons flash a few times, and the phone will reboot. Let go of the power button, but DO NOT let go of the volume down rocker until the while hboot screen comes up. When you see the hboot screen, tell us what it says.
In particular, we need to know if it says s-off or s-on, if it says CID 11111111, and hboot version. Also, if it says LOCKED, UNLOCKED, or RELOCKED.
Official RUU will not run if the bootloader is UNLOCKED (needs to be RELOCKED or LOCKED). But be aware, if the phone is superCID and s-on, running a Jellybean RUU or OTA will brick the phone. Which is one of the reasons we need the bootloader info.
RUU does not need to have stock recovery to run, only OTA does. My guess is your bootloader is unlocked, or its the wrong RUU. Any error message when the RUU fails (if so, what does it say)?
Hi, thank you for your quick reply.
I'm going to write down all that is written in the recovery for i still don't understand what locked or unlocked means, s-on or s-off.
anyway, here goes:
tampered
unlocked
evita pvt ship s-on rl
hboot-1.09.0000
radio-0.16.32.09.01_3
opendsp-v25.1.0.32.0405
emmc-boot
i can't find anything related to cid and i'm still not used to this recovery just yet. wouldn't want to press anything just yet.
i hope i gave enough info and i guess it doesn't look too good just yet.
thank you again for your help.
you should remind me to reduce the use of "just yet".
i'm doing some more reading about superCID and S-on or S-off.
I understand there's a utility from this thread that could determine the supercid status.
http://forum.xda-developers.com/showthread.php?t=1672284
again i'd like to point out i have no clue what has been done to this phone so i am trying to handle it with as much care as possible in order not to brick it.
in case superCID is 1111111 and naturally i don't have the original CID, where would that leave me?
As i am understanding slowly how this phone works, if the previous user managed to install a custom rom and a custom recovery on it, would only make sense to assume the superCID has been modified? (i'll be running the tool shortly unless someone jumps and says NOOOOOOOOO don't do it!!!)
I also noticed the teamwin recovery installed is 2.1.8.1
next is understanding what s-on and s-off are all about.
i have a feeling my chances of reverting to stock firmware are slimming. this is quite a complicated phone, nice challenge.
i'm going to point out again what my main problem is: i can't unlock the sim using the code provided by at&t since as soon as the phone reboots it asks me again. so i don't mind whichever route to take, whether custom or stock, as long as i can unlock the sim the simple way.
cheers.
srasiroslayer said:
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
Click to expand...
Click to collapse
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
srasiroslayer said:
i have a feeling my chances of reverting to stock firmware are slimming.
Click to expand...
Click to collapse
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
redpoint73 said:
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
Click to expand...
Click to collapse
Wunderbar,
Thank you again for clarifying things up.
I've been taking this time to read more about this phone on this thread:
- http://forum.xda-developers.com/showthread.php?t=1671237
So i am starting to understand how it works.
i have to admit that i should consider myself lucky for if the phone had a locked bootloader, it would've been bricked.
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Cheers
srasiroslayer said:
Wunderbar,
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
Click to expand...
Click to collapse
You don't need a Linux environment to get fastboot/adb working. And you will need them if you want to get s-off or change the CID (which would be the solutions to your problem of running the RUU).
To get fastboot/adb going, I'd suggest you start here: http://forum.xda-developers.com/showthread.php?t=1754018
There are some apps what will read the phone's state including CID. Others here have mentioned the name of one (or more) such app, but I can't recall, and I don't use it. I'm used to using fastboot.
srasiroslayer said:
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Click to expand...
Click to collapse
Not sure. Going back to stock might help. Its all I can think of. But don't be disappointed if it still doesn't work.
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
My question is, shouldn't i have the original CID number?
and another off topic point, i have no clue what s-on or s-off are.
i'll get into that reading mode again in a bit.
Thank you again, i feel i'm on the right track now and confident.
Cheers
P.S.: do you need me to post the "fastboot getvar all" results? or only thing missing to be sure of was the CID?
Hang on, you're s-on and SuperCID, don't run the RUU or you'll brick your phone. You need to do some reading and research all this before you try these things.
Sent from my Evita
Guys I am Vivek Rajput, from India. I have AT&T HTC oneX. Anything related to internet is not working except whatsapp. Every app is showing network error msg. Showing some data here which i got after reading here. Assume me complete novice about software/cellphones.
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.320911_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
Have you checked your APNs?
Sent from my Evita
srasiroslayer said:
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
Click to expand...
Click to collapse
If you are going to s-off, you DO NOT want to change the CID. SuperCID (11111111) is needed to s-off.
As mentioned, make sure you s-off before RUU, or you will brick.
Once you are s-off, it shouldn't matter whether you lock the bootloader or not. S-off means all security checks are bypassed, including the check for bootloader lock.
srasiroslayer said:
and another off topic point, i have no clue what s-on or s-off are.
Click to expand...
Click to collapse
s-off, as mentioned above means all security checks are off. There are good and bad points to this.
The good, is that you will be safe of the SuperCID + RUU brick condition. Custom ROMs will also be easier to flash, if you are interested in doing that (do not need to flash boot.img separately).
The bad of s-off, is that because all security checks are off, there are no safety checks to prevent you from flashing the wrong things. You have to be very careful you don't flash something that is not intended for the device, as it may brick the phone.
Are you are okay with that, then proceed with s-off. If not, the alternate solution is to change the CID back to the proper AT&T CID (cws__001). This will also prevent the SuperCID + RUU brick condition. But may make the phone harder to s-off in the future, if you later choose that route.
It looks like then that the s-off route is the one to take, since i will definitely in the future be interested in flashing custom roms.
And it looks relatively easy as per:
http://forum.xda-developers.com/showthread.php?t=2155071
After doing some reading, it also looks safe to achieve s-off on custom roms such as my case.
I'm still reading if s-off will work on my bootloader version or if there are any specific versions to run it at. (so far no mention so good)
I'm guessing i will run s-off today and if everything works out as it should will post my results here.
Only then will i proceed to run the RUU which i downloaded from htc for the at&t model specifically (no chance i could go wrong with that).
Thank you for all the help, i honestly don't think i would've found my way around easily without guidance.
Cheers
Yes, the s-off method is easy, and it should work on any hboot version.
Good luck.
Could just having S-off fix my sim locked issue?
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
srasiroslayer said:
Could just having S-off fix my sim locked issue?
Click to expand...
Click to collapse
I doubt it. SIM lock and s-off are not related, to my knowledge.
srasiroslayer said:
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
Click to expand...
Click to collapse
Once you are s-off, all security and safety checks are off by definition. As long as you are running an RUU meant for EVITA, you will be safe, and it should run properly.
Looks like i got the 99 error thing.
at first i had the error 92 and all was working good but after the final reboot didn't get s-off
the second try i'm getting error 99.
I'm going to read more into it.
I'm still s-on so.......
So here are the current updates.
As i mentioned in the previous post, running it the first time resulted in error 92 which is normal, followed instructions and didn't get s-off.
second time i had error 99. still no s-off.
I turn off the device and power it back on, run the script all over again with a real good attention and precision (i usually don't f*ck things up).
This time i get the error 92 again and still no success at the end. (did this over 4 times now and no s-off).
would i be logical for me to assume that once the rom is booted it's messed up somewhere? hence the last part of the script not working and also hence sim unlock not working?
what's a good custom rom that would i could install using recovery and not brick my phone?
maybe just installing one would solve all my issues.
Cheers
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
timmaaa said:
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm trying it on CleanROM 4.5 beta2.
And by best rom in my case was asking one that would be compatible with my situation, as in hboot 1.0.9, teamwin 2.1.8.1 recovery, supercid, unlocked, s-on.
Cheers.
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...
Hey Folks,
This is my first post in the Sensation forums, i've been reading topics for a few days, but I didn't find any solution to my problem and i'm starting to get annoyed by it.
I've obtained a HTC Sensation a few days ago, and as with my previous devices (Galaxy Gio, Optimus Black) I wanted to flash a custom rom on it. I happened to unlock the bootloader of my friends Sensation few weeks earlier, so i thought this was going to be a piece of cake.
Well it wasn't, I couldn't unlock the bootloader using HTCdev method because the phone is vodafone branded. I tried numerous things, i wasn't able to perform the juopeanutbro (?) trick, tried flashing a custom hboot through fastboot (JB_hboot.zip) in linux (gave me an error 42 "Remote: Custom id check failed" or something like that). And after a few days of trying and trying i'm getting tired of it.
So my question is, is there any option i missed to achieve S-OFF or unlock bootloader? I'd love to flash a custom rom on it because I don't like the 4.0.3 Firmware which the phone is running now.
Phone Details:
Android version: 4.0.3 (vodafone)
HBOOT:1.27.0000
Radio: 11.29A.3504.18_M
CID:VODAPE17
Did you select the Vodafone model there in list of HTC dev...
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium 4 mobile app
Ihttp://forum.xda-developers.com/showthread.php?t=1668276
If htc Dev method doesn't work for your phone, use the non htc Dev method. Follow everything on the screen, do not run out of battery power (that will probably brick your phone)
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Redjack77 said:
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Click to expand...
Click to collapse
has your motherboard been replaced?
what error did you have?
It's not that impossible, I did it in like 10 tries, there are YouTube videos timed exactly so you know when to connect and disconnect the wire. plus you can try as many time as it takes so you really can't go wrong... You know both method require the insulated wire right? It's just one requires the more accurate timing
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Redjack77 said:
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Click to expand...
Click to collapse
what does it say in the top?
juopunutbear or locked?
also i can't view the pics
can you post here in a post?
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://, because i can't include links in my posts as I have lest than 10 posts submitted.
But I actually have solved all my problems, because I knew juopeanutbear had unlocked bootloaders available on his website and in fastboot you are possible to flash these with the command "fastboot oem rebootRUU" wich put the device in RUU update mode, and then flash the unlocked HBOOT from juopeanutbear's website with the command "fastboot flash zip jb_hboot.zip.
Note (to people who might find this useful in the future): The devices sticked on showing a green loading bar in RUU update mode after entering the second command, on the command prompt it showed done, but the device didn't reboot or what. Just wait a while (to be sure) and enter command "fastboot reboot-bootloader"
Now my fastboot screen shows **Juopeanutbear** instead of ***locked*** and I've already managed to flash clockworkmod SUCCESFULLY!!!!!!!
Now I will replace CWM by 4ext and i'm good to go I guess, how I managed to get S-off will remain a secret for me, I assume I did do the wire-trick correctly after all, but didn't notice (you know,, spending a few nights behind your PC doesn't give you a clear state of mind
Redjack77 said:
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://,
Click to expand...
Click to collapse
you are right
i included also the h t t p : //
so you managed it yourself
crongats
now it is time for a custom rom
note: probably after achieving S-OFF you chose no for installing the jb hboot
Running Team Venom's Viper sense 5 rom and just like I expected I LOVE IT!!