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
hi,
first , I dont speak english, so I'm trying little bit and I will use google transalte a lot of time (speak french if somebody do it !)
I can't do mu desire s in s-off, cause the version of hboot is : 2.00.0002
I've tried this solution http://forum.xda-developers.com/showthread.php?t=1443636 but when i'm trying to install rom I have a message error 155 and bad ID (not seems regions !), and I've try to do it with htc supetools and no result !
My phone is root , and unlocked bootloader, an i install 4extrecovery
but since 3 day I'm trying to do it S-off and I can't
is there somebody to help me please ?
Thanks
octopus82 said:
hi,
first , I dont speak english, so I'm trying little bit and I will use google transalte a lot of time (speak french if somebody do it !)
I can't do mu desire s in s-off, cause the version of hboot is : 2.00.0002
I've tried this solution http://forum.xda-developers.com/showthread.php?t=1443636 but when i'm trying to install rom I have a message error 155 and bad ID (not seems regions !), and I've try to do it with htc supetools and no result !
My phone is root , and unlocked bootloader, an i install 4extrecovery
but since 3 day I'm trying to do it S-off and I can't
is there somebody to help me please ?
Thanks
Click to expand...
Click to collapse
Try this one: http://forum.xda-developers.com/showthread.php?t=1604255 >>> This will downgrade your hboot to 0.98.XXXX, read through replies they simplify the steps further.
Then follow this guide: http://www.youtube.com/watch?v=kvg0i8in96M >>> to S-OFF your phone via revolutionary.
It helped me S-OFF my phone. I have same problem like you days ago, i was S-ON, hboot unlocked, rooted and hboot 2.00.0002. Now I'm S-OFF and permanently rooted. Hope this helps!
If I'm not mistaken (and most likely I'm not), you can't downgrade a phone without locking the bootloader first. So you need to lock the bootloader and flash RUU - and you're not using the correct guide for it. You need to do some steps that aren't in the guide.
Jack_R1 said:
If I'm not mistaken (and most likely I'm not), you can't downgrade a phone without locking the bootloader first. So you need to lock the bootloader and flash RUU - and you're not using the correct guide for it. You need to do some steps that aren't in the guide.
Click to expand...
Click to collapse
Correct, but that's after you change your misc version, which is in the guide. Locking the bootloader is part of the steps, so no worries there, RUU's are also there, I think there's one from his region so no problem. Take it from me, I started from S-ON, rooted (temp i think), boot unlocked and hboot 2.00.0002 and the guide is noob fail-safe, given you researched enough to know what you're doing, and you just do what it tells you. You'll do the deed right.
Sorry, I was replying to the OP, but you posted before me so it looks like I'm replying to you instead. I meant the guide he mentioned in his OP, not your guide.
bods11 said:
Try this one: http://forum.xda-developers.com/showthread.php?t=1604255 >>> This will downgrade your hboot to 0.98.XXXX, read through replies they simplify the steps further.
Click to expand...
Click to collapse
Thank's
I tried this, but the last step does not work with me, I can not bring the command line because cmd does not detect my phone when it is in bootloader, or maybe I'm wrong to maneuver?
Code:
then type in command prompt.
- fastboot oem lock
P.S: the bootloader is unlock with htcdev.com
bods11 said:
RUU's are also there, I think there's one from his region so no problem.
Click to expand...
Click to collapse
What do you mean by "region": is the region where I live, or that or the phone was for its manufacture? if this is the second time how to recognize the region because I have not bought new?
thank's
Before starting with everything, turn on USB Debugging (settings>developer options) and turn off Fast boot (settings>Power) in your phone.
You installed HTC sync in your PC right? If not, first download and install HTC Sync (from here www(dot)htc(dot)com/sea/help/htc-desire-s/#download), you need the drivers from HTC sync, so your pc can recognize your phone.
Make sure you rebooted to bootloader. Then enter:
- fastboot oem lock >>> this is to "relocked" your phone so you can proceed to installation of the RUU.
First and foremost, is your phone branded? If yes, then choose the right RUU for you. If no, you can use the unbranded RUU. Or you can search the forum for your specific region, I think Europe RUU is ok. "Region" is your area, where you live and use your phone. Im from south east asia, so i used asia RUU. Also take note of Post #5 of the first guide, he has summarized everything and i believe he's in the same region as you. Read through everything before starting.
bods11 said:
Before starting with everything, turn on USB Debugging (settings>developer options) and turn off Fast boot (settings>Power) in your phone.
You installed HTC sync in your PC right? If not, first download and install HTC Sync (from here www(dot)htc(dot)com/sea/help/htc-desire-s/#download), you need the drivers from HTC sync, so your pc can recognize your phone.
Make sure you rebooted to bootloader. Then enter:
- fastboot oem lock >>> this is to "relocked" your phone so you can proceed to installation of the RUU.
First and foremost, is your phone branded? If yes, then choose the right RUU for you. If no, you can use the unbranded RUU. Or you can search the forum for your specific region, I think Europe RUU is ok. "Region" is your area, where you live and use your phone. Im from south east asia, so i used asia RUU. Also take note of Post #5 of the first guide, he has summarized everything and i believe he's in the same region as you. Read through everything before starting.
Click to expand...
Click to collapse
I relocked bootloader, maked a gold card, tried to install rom with fastboot usb and normaly, then the message error turn to ERROR [131]: ERROR CUSTOMER ID, before it was ERROR [155]: ERROR IMAGE
what can t do now ?
thanks
You flashed the wrong ROM for your CID, and the goldcard isn't correct.
Jack_R1 said:
You flashed the wrong ROM for your CID, and the goldcard isn't correct.
Click to expand...
Click to collapse
GOD IS GREAT GOD IS GREAT GOD IS GREAT
Thursday night is that I try to put it into s-off and to change the rom and the problem was the wrong way to do a Goldcard (I did it with goldcardtool)
here is the good way to do a goldcard
http://androidforums.com/desire-s-all-things-root/500543-guide-how-create-goldcard.html
I found it through dan fish in this topic
http://forum.xda-developers.com/showthread.php?p=27529821
Thank you so much dan fish and everybody who who tried to help me !
and now it's S-off with revolutionnary !
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!
Hi all.
I have A HTC Sensation, on Orange (UK).
The handset was completely standard, untouched. I have followed the guide to unlock my bootloader using HTC dev.
It seemingly worked, and I held volume down and pressed power and verified that the text at the top said "UNLOCKED". great
When I booted the phone, it gave me the "fresh start" intro screens, which I followed through on.
Once completed, the phone loaded to the normal home screen, but now gets no signal. Its always 0 bars and "NO SERVICE" warning.
Only thing I have done is as above, so unsure what could have gone wrong?
Only thing I can think is that I chose the wrong "what phone do you have" option on HTCDev. I chose HTC Sensation (EU), as the phone is not on tmobile, and not vodafone, and IS european. However, tmobile and orange are now part of the same umbrella company, so perhaps something bad happened there?
Unsure what I should do next? Re-lock the bootloader? Any suggestions very gratefully welcomed! Thanks
Hmm.. that's really weird. Unlocking the bootloader doesn't affect your cell phone signals. I would run a RUU and see if that fixes the problem.
Here's the guide: http://forum.xda-developers.com/showthread.php?p=26541170
Follow steps 2&3.
Before you do, try taking out your sim and putting it back in. I highly doubt you put your sim in the wrong way, but I did this before (I don't think I'm the only idiot out there)
Sent from my HTC Sensation
Thanks. I'll follow that guide.
SIM card is in OK. Was I supposed to remove the SIM when I was unlocking the bootloader? I didn't do that.
Just waiting for the RUU file to download.
The guide says I need one with a higher or equal version to my main version. My main version is 3.x and the highest version I can find via the links in the guide are 1.x. Will this be ok?
I'm really not sure how the phone got this screwed up.If I did select the incorrect device type in HTCDev (i.e. I selected Sensation EU and should have selected Sensation Tmobile) would that possibly cause this problem?
Would it be worth re-locking, then unlocking using the tmobile device? Guessing I would be supplied with a different unlock_code.bin?
EDIT: Just checked and the tmobile device choice is actually for "tmobile USA", so looking like I chose the correct device after all.
RUU I had failed. As I say my version is 3.x and this was 1.x so I'm not surprised.
My exact version reads: 3.32.61.51
Can anyone suggest a RUU file that I can have a go with, or any other suggestions?
Bootloader is currently RELOCKED.
Thanks
Did you try this ruu?
http://www.shipped-roms.com/downloa...0U_10.51.9007.27_M3_release_198549_signed.exe
EDIT: try looking for your ruu here: http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98
The general ROM section has 3.32 versions.
Sent from my HTC Sensation
Yes, I tried the first one you posted, which wouldnt work (too old presumably).
I will try one of the unbranded ones; but unsure if they are suitable as I have an Orange logo when I boot?
Thanks
Still waiting for the RUU to download, so will probably carry on looking at this in the morning now.
A little more info that might give someone an idea:
If i go into settings, and click on "Mobile settings" and go to choose carrier, the phone searches for carriers.
25% of the time it says "no network found"
75% of the time, it finds O2.
25% of the time it finds 3 or vodafone
It never finds orange. It seems it IS looking for networks though?
If I put the SIM card in my very old dumb-phone, it finds orange fairly quickly and connects.
Thanks for any help
There's another option. You can try to s-off your phone with ganeshp's guide and then flashing the 3.33 firmware which contains the newest radio and stuff.
Here's s-off guide without HTC dev unlock: http://forum.xda-developers.com/showthread.php?p=26280760
Here's the firmwares for sensation: http://forum.xda-developers.com/showthread.php?p=21711154
Sent from my HTC Sensation
AndroidSupporter318 said:
There's another option. You can try to s-off your phone with ganeshp's guide and then flashing the 3.33 firmware which contains the newest radio and stuff.
Here's s-off guide without HTC dev unlock: http://forum.xda-developers.com/showthread.php?p=26280760
Here's the firmwares for sensation: http://forum.xda-developers.com/showthread.php?p=21711154
Sent from my HTC Sensation
Click to expand...
Click to collapse
actuallly it is better to use auggie2k's guide because he has done htcdev unlock
But he relocked it... on the 5th post
Sent from my HTC Sensation
Hi guys
Thanks to you both for your suggestions.
This morning I unlocked the phone once more, and still had limited service. I then re-locked once again, and as soon as the phone booted it had full service, and has done ever since.
I have no idea what went wrong (they HTC Dev article is pretty straightforward, so I don't think I did anything wrong), and the action that I did above (unlock, relock) I must have done 5 times last night without any effect.
I am still determined to root the phone, so will probably end up with another broken handset soon But at least I will be doing it at the weekend this time, instead of midnight on a Thursday when I have to work at 7 the next day!
Thanks for all the help, I'm sure I'll be back with more questions (problems!) soon.
No problem! Glad to try to help
Sent from my HTC Sensation
Following this minor hiccup (still no idea why it happened) I've now got managed to:
Unlock
Root
Install recovery
Get SU
Get S-off
So thanks for all the help. I'm a complete beginner, but the guides on this site are great and really easy to follow.
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.