Related
Please please forgive the newb question, but once the bootloader is officially unlocked by HTC's method (basically entering a token you pull from your phone, and then flashing a .bin file they send you based on that token), is it reversible? I.E. is it possible to re-lock it back to factory status? I'm assuming not, but can't find any hard evidence one way or the other...
Apparently someone has said you can re-lock it but I've not used it. Better using Revolutionary IMO
Well you can do a "simple" re-lock just to ensure noone else can make changes to it with "fastboot oem lock" - but it's not the factory lock. The bootloader simply says "re-locked" instead of "unlocked", or compared to the factory "locked".
But I was thinking in terms of reverting it truly back to factory status. Again, I don't think it's possible (without HTC's intervention anyway), given the nature of how it was locked, but need someone smarter than me to confirm that suspicion.
So basically, using Super CID, you can run the RUU.exe from the bootloader only, and get your phone back to 100% stock, but it'll still be unlocked. So I'm guessing there is no way to reverse HTC's unlock process.
jntdroid said:
So basically, using Super CID, you can run the RUU.exe from the bootloader only, and get your phone back to 100% stock, but it'll still be unlocked. So I'm guessing there is no way to reverse HTC's unlock process.
Click to expand...
Click to collapse
I flashed the android revolution rom with my device unlocked through htc website, I cannot flash back to stock, I tried the RUU to bring me back to 1.27 and 1.29 and error'd on both of those. I am not sure how to get back to stock. I tried several times. I also cannot get my security to turn off in the bootloader after I unlocked through htc. Has anyone figured out how to do this? I tried the revoltionary.io tool and successfully used the tool only to reboot and see the S-ON in bootloader mode. CRAZY I suggest for anyone to turn their S-OFF using revolutionary.io before they ever attempt to unlock the bootloader through htc. What I am experiencing is error under the wifi switch I cannot seem to get wifi working with any of the roms, probably due to the kernel or not having s-off in bootloader. I tried different and stock kernels only to have the same problem.
Read this if you want more info: http://forum.xda-developers.com/showthread.php?t=1290395
Has ANYBODY tried the goldcard method to reflash to stock? Take the rom.zip from RUU and flash in bootloader
So ive gone back to stock htc orange ROM with the CID ORANG001 and i am now also S-On after being on ARHD, after probelms with the phone in case i need to send it back, so by the looks of what you are saying I am not actually back to factory status? So will HTC be able to tell in the case that i have to send it back fro repair or whatever? If so i also need to know how to re lock and get back to complete factory status!?
EDIT: im pretty sure bootloader was already available on the phone, and my firends incredible s, he is able to access bootloader without doing anything to his phone
Gold card doesn't work, otherwise we could've used it before S-OFF
gtcalder said:
So ive gone back to stock htc tmobile ROM with the CID ORANG001 and i am now also S-On after being on ARHD, after probelms with the phone in case i need to send it back, so by the looks of what you are saying I am not actually back to factory status? So will HTC be able to tell in the case that i have to send it back fro repair or whatever? If so i also need to know how to re lock and get back to complete factory status!?
EDIT: im pretty sure bootloader was already available on the phone, and my firends incredible s, he is able to access bootloader without doing anything to his phone
Click to expand...
Click to collapse
Where is this CID ORANG001 you are referring to? Do you have a link? And as far as I know you can unlock the bootloader but there is currently no true relock.
droiddv said:
Where is this CID ORANG001 you are referring to? Do you have a link? And as far as I know you can unlock the bootloader but there is currently no true relock.
Click to expand...
Click to collapse
Hi, list of CIDs for each ROM..
http://forum.xda-developers.com/showthread.php?t=1195475
Hello,
I have maybe a stupid newb question. I've been searching around for an answer but with no luck.
My problem is as follow:
I've been using HTC Sensation for half a year now, with custom roms / rooted / SuperCID. So I'm not new to flashing stuff.
Somehow I managed to brick my device before (due to stupid flashing decisions). So I flashed a random EU RUU and send my phone for repairs (via insurance services). They "repaired" my phone. I'm not sure if I got a new one or they really repaired it? (IMEI changed but S/N is still the same)
Today I got my HTC Sensation back. I was very happy and started to check the phone. It appears the bootloader is locked and S-ON. (CID back to T-MO003)
So I tried to S-OFF using revolutionary.io , to bad without luck...
I started searching what might be the problem read something about downgrading and revolutionary works... got a bit confused about all the different posts around.
What is the correct way to get S-OFF, custom recovery, and so on... back on my phone?
Bootloader info:
Locked
S-ON
HBOOT 1.18.0000
Aug 2 2011.22:35:52
Thanks for your time!
Hoping for a fix,
Opletium
?????
how much did you end up paying for repairs
Nothing haha, I was suprised about that!
normally my insurance company bills 30 euro as "own risk".
I've read the agreements of the insurance and saw that damage caused to the phone by falling on the ground was covered. My phone had some visable damage on the egdes.
So I told the insurance that i dropped my phone. And because it stopped working i tried to reinstall the sofware to factory defaults.
What I did is: I flashed a RUU and that caused the brick, because the touch panel stopped working.
They "fell" for it.. kinda
ok tried to follow this guide:
http://forum.xda-developers.com/showthread.php?p=21922297#post21922297
problem, cant get my bootloader unlocked. HTCdev's unlock fails.
Error i get:
C:\bootloader_unlock>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.140s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.156s
File is in place, tried it multiple times and tried multiple tokens.. no clue on this!
Anyone that can help me to unlock and S-Off my device?
Did you try Revolutionary?
yes, I tried, but keeps failing aswel..
kinda start hating TMO for branding all their phones
This is the output of revolutionary
Enter beta key [ serial: HT17PV800204 ]: 47YUAhIWs2BusHJc
Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so.. Failed to get Root!
Press (almost) any key to exit.
Click to expand...
Click to collapse
is USB Debugging activated?
also have you got the drivers from HTC sync installed, but sync uninstalled, together with any other software that might attempt to sync with the phone?
USB debugging tried both enabled and disabled.
HTC drivers version 3.0.0.007 installed.
no other software on my laptop or PC that use my phone.
The thing that confuses me is that after repairs my IMEI number changed but my S/N stayed the same.
Guess they only replaced some hardware and not the total phone..
if that is the case then we should be aware that this HTC Sensation was S-OFF / rooted before.
When my touchpanel stopped working I flashed a RUU and locked bootloader and put the phone back to S-ON. I believe that I was on a lower version HBOOT while I send the phone back (before the phone went for repairs).
Try this
or try unlocking at HTC.
maumont said:
Try this
or try unlocking at HTC.
Click to expand...
Click to collapse
HTC Unlock does not work!! I have explained that a few posts back.
I tried your link... after the command
adb shell /data/local/tmp/tacoroot --root
Click to expand...
Click to collapse
my phone is bootlooping..
Ok did a factory reset via bootloader, now my phone works again.
but still no S-OFF..
The problem most likely is that you entered your details incorrectly at the HTC Dev site for unlocking your bootloader.
I don't think it checks the serial number to be genuine, I think as long as it follows a certain format it's accepted, so I would certainly check what you entered and try re-downloading the file from the Dev site. It's clearly NOT a driver issue, as CMD wouldn't even push the file to the phone if it was.
Hope this helps
Opletium said:
HTC Unlock does not work!! I have explained that a few posts back.
I tried your link... after the command
my phone is bootlooping..
Click to expand...
Click to collapse
Redo the taco root method. your phone will boot loop. don't restart and while bootlooping redo revolutionary. that worked for me. press the tanks button if it work for you .
khanem said:
Redo the taco root method. your phone will boot loop. don't restart and while bootlooping redo revolutionary. that worked for me. press the tanks button if it work for you .
Click to expand...
Click to collapse
Doubt this will work for them, as Revolutionary won't work without an Unlocked Bootloader and this is where they are getting stuck.
Just had contact with HTC themself to ask why the htcdev.com method is not working for me.
They explained that T-Mobile NL put their software on my phone while I send it for repairs. they put their bootloader on my phone, first i was like WTF but then he started mumbling about update that htcdev-tool does not support yet.. after some more " doubt-talk". He asked some software versions and made a case he would put trough to the technical support.
Guess that explains the HTCDev problem?????
/edit: I have tried over 15 times on the htcdev.com method
if I understand jaaystott correctly then first you need to have an unlocked bootloader in order to use revolutionary to S-OFF??
Any otherway to unlock the bootloader, because this htc method will take some time..
As for:
Redo the taco root method. your phone will boot loop. don't restart and while bootlooping redo revolutionary. that worked for me. press the tanks button if it work for you .
Click to expand...
Click to collapse
never tried it this way but I cant imagine that it would work since the bootloader is still locked.
Flash some other offical RUU, that should do it
jaaystott said:
Doubt this will work for them, as Revolutionary won't work without an Unlocked Bootloader and this is where they are getting stuck.
Click to expand...
Click to collapse
Taco root will give revolutionary access to files he cannot modify before. In all cases he can try if it doesn't work he will have to unlock first with htcdev then redo the whole operation.
Opletium said:
Just had contact with HTC themself to ask why the htcdev.com method is not working for me.
They explained that T-Mobile NL put their software on my phone while I send it for repairs. they put their bootloader on my phone, first i was like WTF but then he started mumbling about update that htcdev-tool does not support yet.. after some more " doubt-talk". He asked some software versions and made a case he would put trough to the technical support.
Guess that explains the HTCDev problem?????
/edit: I have tried over 15 times on the htcdev.com method
if I understand jaaystott correctly then first you need to have an unlocked bootloader in order to use revolutionary to S-OFF??
Any otherway to unlock the bootloader, because this htc method will take some time..
As for:
never tried it this way but I cant imagine that it would work since the bootloader is still locked.
Click to expand...
Click to collapse
Yes thats correct. Until the Bootloader is Unlocked nothing can be installed other than apps from the Market
As for the problem, I highly doubt that it's T-Mobile's Bootloader, I mean surely loads of other people on OTA's would have had this issue.. surely somewhere someone has reverted to stock and then realized that this is the problem?
I think it's likely the change of IMEI might have done it, could be the wrong IMEI associated with that Serial Number and so it won't flash.
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
Your CID should be 11111111, so you can unlock your bootloader again using the same unlock token from your first unlock. You will need HTC drivers installed.
to relock your bootloader,
Fastboot files http://www.mediafire.com/?4dx982z93w8z7wk
download and extract to desktop
open cmd and type cd Desktop
then cd foldername (the folder where fastboot is)
Boot into fast boot on your phone
then type fastboot oem lock
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
It will break root, but you can get that back with one of the original ways since you will still be on 1.85.
Sent from a slithery smooth phone!
Just flash another rom or wipe and reflash. Ruu will probably not help a random reboot.
Yeah same, I'd try a different ROM without going back to stock just to come to custom ROMs again.
WR
Sent from my One X
crazylilazn said:
Hi guys, so after having some trouble with my phone randomly rebooting while running ViperXL, I've decided to relock my bootloader, reload the RUU 1.85 firmware, and then re-unlock my bootloader. However, I'm not really sure how to go about doing this.
I've had my phone since it came out on AT&T, and I *think* I was on the 1.85 firmware back when I rooted it. I only recently unlocked the bootloader and installed the ViperXL ROM, so now I'm not too sure as to what RUU I was on before.
So, I have a couple of questions I was hoping somebody would be able to answer:
I looked through the indexed compilation, and I didn't seem to find anything that would help me relock the bootloader. Could someone help lead me in the right direction?
Additionally, on the Stock RUU 1.85 for Cingular forum page, there's a notice saying that it "breaks the current root exploit". I'm not too sure what to make of that, considering that it was last updated in May. However, my phone was rooted back in June-ish, so I'm not sure if that root exploit is the same exploit that they are alluding to. Would i possibly have to re-root my phone afterward?
Lastly, after getting the stock RUU installed, is there a different process that I need to go through to re-unlock the bootloader considering that I was already unlocked before? Or do I need to follow the same exact procedure I did the first time?
Thanks for the help, and I apologize for the length of this forum post.
Click to expand...
Click to collapse
this has answers to all your questions http://forum.xda-developers.com/showpost.php?p=26669144&postcount=1
enjoy the read...
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.
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!!