Hello,
I am quite confused about the term SuperCID and what it means. My sister got a HTC One S. I unlocked and unrooted it for her quite a long time ago. Now, I want to get S-off but I can't do it because I don't have SuperCID. I read on the forum and some people say that Super CID means your phone is unlocked, while other say you have to use the command "fastboot oem readcid" to check if you get SuperCID.
I use "fastboot oem readcid" on the HTC One S and it shows TMOB010. Then does that mean that I don't have SuperCID? Then what exactly is SuperCID when the HTC One S is already shown "Unlocked and Tampered" on the fastboot screen. Pleas let me know. I am quite confused with all this terminology. I can look up direction to get SuperCID but I want to be sure that the phone has it or not before I proceed.
Thank you for your help
vi6s said:
Hello,
I am quite confused about the term SuperCID and what it means. My sister got a HTC One S. I unlocked and unrooted it for her quite a long time ago. Now, I want to get S-off but I can't do it because I don't have SuperCID. I read on the forum and some people say that Super CID means your phone is unlocked, while other say you have to use the command "fastboot oem readcid" to check if you get SuperCID.
I use "fastboot oem readcid" on the HTC One S and it shows TMOB010. Then does that mean that I don't have SuperCID? Then what exactly is SuperCID when the HTC One S is already shown "Unlocked and Tampered" on the fastboot screen. Pleas let me know. I am quite confused with all this terminology. I can look up direction to get SuperCID but I want to be sure that the phone has it or not before I proceed.
Thank you for your help
Click to expand...
Click to collapse
SuperCID will be a seven digit string of the same number (1111111, 2222222 etc). These CIDs gain special access to partitions normally locked down (how they test stuff). Having this CID means you can do more stuff, meaning write different sectors etc.
So TMOB010 means you don't have it.
To make a complete answer; unlocked is just when you unlock your phone via HTC's website which allows you special access to partitions and fastboot, however not all partitions are accessible - whereas with SuperCID you can access them all.
ZackehSoul said:
SuperCID will be a seven digit string of the same number (1111111, 2222222 etc). These CIDs gain special access to partitions normally locked down (how they test stuff). Having this CID means you can do more stuff, meaning write different sectors etc.
So TMOB010 means you don't have it.
To make a complete answer; unlocked is just when you unlock your phone via HTC's website which allows you special access to partitions and fastboot, however not all partitions are accessible - whereas with SuperCID you can access them all.
Click to expand...
Click to collapse
correction.
supercid does not allow special acces of different partitions, who told you that.
its just a masterkey for stock softwareversion implementation, nothing more.
its either a eng-hboot or a s-off implementation that gives you that freedom.
real187 said:
correction.
supercid does not allow special acces of different partitions, who told you that.
its just a masterkey for stock softwareversion implementation, nothing more.
its either a eng-hboot or a s-off implementation that gives you that freedom.
Click to expand...
Click to collapse
That's incorrect. You can have a stock HBOOT and be S-ON with SuperCID. SuperCID isn't the implementation, it's a way to gain the implementation. And it allows you special access in that it's a masterkey...
Example; I gain S-OFF with Moonshine. Does that mean I have SuperCID? No. Does that mean I have an ENG HBOOT? Yes. Can I reflash that HBOOT to stock and keep S-OFF? Yes.
SuperCID allows the flashing of any ROM regardless of the carrier it was meant for (special access) and it also allows for the writing of Ext_ROM (special access, again - see CID LOCK).
ZackehSoul said:
That's incorrect. You can have a stock HBOOT and be S-ON with SuperCID. SuperCID isn't the implementation, it's a way to gain the implementation. And it allows you special access in that it's a masterkey...
Example; I gain S-OFF with Moonshine. Does that mean I have SuperCID? No. Does that mean I have an ENG HBOOT? Yes. Can I reflash that HBOOT to stock and keep S-OFF? Yes
SuperCID allows the flashing of any ROM regardless of the carrier it was meant for (special access) and it also allows for the writing of Ext_ROM (special access, again - see CID LOCK).
Click to expand...
Click to collapse
No supercid is just a generic cid.
It has no hardware advantage over a stock cid. It's mainly used for unbranding.
I always have my devices on stock hboot and stock cid. Only s-off is what I want.
Haven't found anything I couldn't flash.
Like your link says VENDERLOCK thus software.
It's the unlock (xda-dev) part that provides the access of certain partitions.
With s-off even more is available.
S-off and hboot have no direct relation.
Example: Lower stock hboots can flash radio with only a unlocked device. Higher can't.
What's the difference a device unlocked supercid and a device unlocked unbranded cid. ?
Is there any rom custom that can't be flashed with just unlocking,
Lets make it supercid can I flash more roms?
Its just an coincidence that with the newer devices supercid was needed for getting s-off. It didn't used to be that way.
Hell easy unlocking didn't even exist.
It was s-off or bust mostly.
The link you give is not that clear.
ext_rom have you read there description?
I don't think that's a really secured partition. Do you?
Typing on a phone is fukd if it gets to big.
Verstuurd van mijn HTC One S met Tapatalk
real187 said:
No supercid is just a generic cid.
It has no hardware advantage over a stock cid. It's mainly used for unbranding.
I always have my devices on stock hboot and stock cid. Only s-off is what I want.
Haven't found anything I couldn't flash.
Like your link says VENDERLOCK thus software.
It's the unlock (xda-dev) part that provides the access of certain partitions.
With s-off even more is available.
S-off and hboot have no direct relation.
Example: Lower stock hboots can flash radio with only a unlocked device. Higher can't.
What's the difference a device unlocked supercid and a device unlocked unbranded cid. ?
Is there any rom custom that can't be flashed with just unlocking,
Lets make it supercid can I flash more roms?
Its just an coincidence that with the newer devices supercid was needed for getting s-off. It didn't used to be that way.
Hell easy unlocking didn't even exist.
It was s-off or bust mostly.
The link you give is not that clear.
ext_rom have you read there description?
I don't think that's a really secured partition. Do you?
Typing on a phone is fukd if it gets to big.
Verstuurd van mijn HTC One S met Tapatalk
Click to expand...
Click to collapse
Yeah exactly it removes the vendor lock which gives you access to write partitions you otherwise wouldn't be allowed to in that way.
I think we're actually arguing the same point here dude Think I misread your point about HBOOT in the second post.
ZackehSoul said:
Yeah exactly it removes the vendor lock which gives you access to write partitions you otherwise wouldn't be allowed to in that way.
I think we're actually arguing the same point here dude Think I misread your point about HBOOT in the second post.
Click to expand...
Click to collapse
Hmm...., so, based on the info, it means SuperCID is not that different from generic CID. However, you need it to get S-Off, which in turn allows you to write to different partition. Because my ultimate goal is to get S-off to update my sister phone to the CyanogenMod 10.2. Is that correct or did I miss anything?
vi6s said:
Hmm...., so, based on the info, it means SuperCID is not that different from generic CID. However, you need it to get S-Off, which in turn allows you to write to different partition. Because my ultimate goal is to get S-off to update my sister phone to the CyanogenMod 10.2. Is that correct or did I miss anything?
Click to expand...
Click to collapse
Blunt answer: you need superCID for S-OFF, unlock isn't enough by itself.
Related
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Hi,
This is a SENSATION forum.
malybru said:
Hi,
This is a SENSATION forum.
Click to expand...
Click to collapse
Yes I noticed it i already asked the moderation if they could move the thread to the Desire S section.
I need to find this out to? I dont want to root my Desire S, I just want to changde CID so i could put unbranded software to it...?
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
doghous said:
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
Click to expand...
Click to collapse
Yes I know that works I have a Goldcard. The thing here is that I would like the phone to be completely unbranded without the need os special cards so in case i want to sell it or send it to warranty it won't be noticed that i changed something there. So if there is a way to re write de CID it would be good.
Well i actually successfully installed the unbranded european ROM 1.28.401.1 using the gold card. But now i can't receive OTA updates. Is there a way to get it to work?
Why don't you run the European RUU 2.10 version (RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed) from the following link:
http://forum.xda-developers.com/showthread.php?t=1002506
That's what I did
smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Skanob said:
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Click to expand...
Click to collapse
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
smash_07 said:
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
Click to expand...
Click to collapse
The goldcard does not alter the CID. It just tells the bootloader to ignore the CID check when running a RUU.
One way to alter the CID is to XTC clip the phone.
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
smash_07 said:
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
Click to expand...
Click to collapse
My reply to this post of yours is already a hint.
Use search PLEASE.
what are the benefits of doing super-CID (i.e. 11111111)
If i do superCID can I again restore to stock CID..
Please help
abhishek89 said:
what are the benefits of doing super-CID (i.e. 11111111)
If i do superCID can I again restore to stock CID..
Please help
Click to expand...
Click to collapse
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
So how do I install roms from different carriers
fatswaller4451 said:
So how do I install roms from different carriers
Click to expand...
Click to collapse
first you need to S-OFF then supercid
after that you can use any ruu.exe
Super Cid
rzr86 said:
first you need to S-OFF then supercid
after that you can use any ruu.exe
Click to expand...
Click to collapse
Hey thanks for your response
Ok so I have s-off and super Cid just a few more questions if u don't mind
1. can i install any ruu for any android phone or am I limited?
2. Will installing a ruu for another phone effect the way my current phone works
3. When installing a ruu.exe for another phone will I have to follow the same bootloader unlock method for that phone or my phone?
Sorry for the newbie questions but I have limited knowledge of super cid however I have been rooting for years now
I heard some bad things about super cid but have not had any issues thus far, the guide was very easy to follow and in fact just to make sure it was working I was able to ruu backwards
Thanks for your expertise you r awesome
fatswaller4451 said:
Hey thanks for your response
Ok so I have s-off and super Cid just a few more questions if u don't mind
1. can i install any ruu for any android phone or am I limited?
2. Will installing a ruu for another phone effect the way my current phone works
3. When installing a ruu.exe for another phone will I have to follow the same bootloader unlock method for that phone or my phone?
Sorry for the newbie questions but I have limited knowledge of super cid however I have been rooting for years now
I heard some bad things about super cid but have not had any issues thus far, the guide was very easy to follow and in fact just to make sure it was working I was able to ruu backwards
Thanks for your expertise you r awesome
Click to expand...
Click to collapse
1)with s-off and supercid you are not limited
2)it won't affect anything at all
But probably you will have some official updates from the specific carrier(if you have)
3)I think it depends from the carrier of the Ruu you have chosen
But actually there is no need to unlock the bootloader because you are on s-off
Edit:in second and third question what do you mean by another phone?
I assume you mean another carrier
If yes then yes
If you mean another device(for example Samsung)then absolutely no
Of course you can use any ruu but only from sensation's devices
Sent from my HTC Sensation using xda premium
super cid
rzr86 said:
1)with s-off and supercid you are not limited
2)it won't affect anything at all
But probably you will have some official updates from the specific carrier(if you have)
3)I think it depends from the carrier of the Ruu you have chosen
But actually there is no need to unlock the bootloader because you are on s-off
Edit:in second and third question what do you mean by another phone?
I assume you mean another carrier
If yes then yes
If you mean another device(for example Samsung)then absolutely no
Of course you can use any ruu but only from sensation's devices
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
So I have verified that I have super cid on my evo 4g lte by ruuing backward, however when I try flashing an htc one ruu i get an error message that its the wrong file, so i tried flashing an original evo 4g ruu and still get the same message
I am still s-off
relocked bootloader
super cid
hboot 2.0.9
latest firmware
am i missing something?
Thanks
fatswaller4451 said:
So I have verified that I have super cid on my evo 4g lte by ruuing backward, however when I try flashing an htc one ruu i get an error message that its the wrong file, so i tried flashing an original evo 4g ruu and still get the same message
I am still s-off
relocked bootloader
super cid
hboot 2.0.9
latest firmware
am i missing something?
Thanks
Click to expand...
Click to collapse
wait man man
for which device are we talking about?
not for sensation?
EVO 4g lte
Sent from my EVO using xda app-developers app
fatswaller4451 said:
EVO 4g lte
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
no maaaaannnnn
don't use any ruu for sensation to evo 4g
go to the evo 4g's thread and see there for ruu.exe files
this forum is only for sensation/xe/4g
i thought you were talking about sensation devices
Ok thanks for the info but I was talking about super cid and installing roms from different carrier's
Sent from my EVO using xda app-developers app
---------- Post added at 12:14 PM ---------- Previous post was at 12:06 PM ----------
I was following a previous thread
Sent from my EVO using xda app-developers app
to reduce the confusion
NO- you cant/shouldn't flash another model phone's RUU on another
there is a high chance of bricking the device if you do that
Does SuperCID also network unlocks the phone?
There is a lot of confusion on the internet about SuperCID. I have HTC One S which is locked to T-Mobile and I want to get it network unlocked. the "strings -n 8 /dev/block/mmcblk0p6" method did not show unlock_code for my phone (though it has worked for some other people). While googling I found that doing SuperCID by changing mmcblk0p4 can also network unlock the phone. Please let me know if you have some idea. Thanks.
gol_n_dal said:
Certain things, e.g. RUUs, need to have the correct Carrier ID on the phone in order to install via the bootloader or recovery using the PG58IMG.zip process. The Latest Firmware packs for example are grouped together into sets, this is to allow you to install them if you don't have SuperCID. If you have got SuperCID you can install any of them as all the CID checks pass.
Another reason to change the CID if to allow you to install a generic RUU instead of the one that came with the phone, this allows you to remove the bloatware. For example I'm on Vodafone and I installed the generic Euro RUU purely to get rig of the Vodafone crap that came pre-installed.
The process to change it back is identical to the way you write the SuperCID just using your original CID (mine for example is VODAP001). IIRC HTC__01 is the generic CID
Click to expand...
Click to collapse
Hey man, before S-OFF, why we should do unlock bootloader via htcdev? (my hboot is 1.27.000)
What is the purpose to do that?
Can you explain this for me?
Thanks..
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
the first version of doing S-OFF requires htcdev unlock but the second one does not require
if you do not want to use htcdev unlock method for doing S-OFF method after see this thread
http://forum.xda-developers.com/showthread.php?t=1661631
he was refering more to the purpose of HTC Dev unlocking i guess
this is what i found but it is outdated (2009) dunno whether something has changed or not, so maby some nerds can explain further for him
DigitalPioneer said:
OK, about sixteen million posts have been flying back and forth about what you can do with root, can't do, what S-OFF is, is not... So I'm going to try to clear it all up for you, OK?
ROOT means you have full control over the OS. From the OS, you can write to the recovery partition. Without root, the only way to write recovery is through hboot, which will only let you flash a custom recovery if you have S-OFF. But even with S-ON, you can write recovery from the OS if you have root. Then, with a custom recovery, you can write the hboot with an engineering bootloader, which has S-OFF. This way, you get S-OFF without a warranty-voiding watermark.
S-OFF means you can flash a custom recovery or ROM from hboot. Things you could already do with root, except that it's hard to get root while S-ON. But if you get it, you're set.
HTC says they'll ship an update which sets S-OFF, and then we're set, except their update will almost assuredly drop a watermark and void the warranty.
ANALOGY: Say the phone is a fortress, and you're trying to get in. S-ON means the gate is shut. If you root it with S-ON, you do it with an exploit, so you find a weak spot in the wall and pack it full of C4 and BOOM, you're in. S-OFF means they opened the gate from the inside, and you just walked in. Either way (S-OFF or root) you're in.
SUMMARY: With S-OFF, you get everything. With root, you get everything. End of story.
Final comment: rooting with S-ON means you used an exploit. Exploits are bad!! But HTC is forcing us to resort to such brutish, nasty means (blowing up walls to the fortress) because they locked the gate before selling us the place. We have a right to get inside, but they aren't opening the gate, so we have to get in some other way. Remember, if you can blow up the wall and walk in, a malicious program can do so too. Exploits are bad, and HTC should patch them. But let's get some legitimate use out of them first, ehhh?
Click to expand...
Click to collapse
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.
I am merely posting this here for all those considering to go S-Off but haven't found the courage for it yet or just aren't sure what S-Off actually is. So to ease your minds a little bit I wish to explain S-Off.
For starters, S-Off and root ARE TWO COMPLETELY DIFFERENT THINGS!
HTC has been securing their phones by locking the internal flash memory (NAND or eMMC)(eMMC in our case) to stop it from being written to, unless the file being flashed is signed by a private key only known to HTC. This is controlled by a flag (@ secuflag) and is identified as the device being S-ON. Telling the HBoot the device is Security Off (S-OFF) stops this check for the key, and allows us to write anything to any partition, which is what we are aiming for.
There are actually two levels of S-OFF. The Bootloader (HBoot) and the Radio. Getting S-Off on the HBoot gives us everything we need, but doesn't actually turn off the @ secuflag which is set in the radio - instead, the HBoot ignores it and therefore thinks it is S-Off, but this is not TRUE S-Off. It is possible to flash a HBoot that believes the Radio is set to S-OFF, as the HBoot is responsible for setting that flag.
Once the HBoot on the phone is S-OFF, we can write to all the partitions and basically do whatever we want, but it is possible to go one step further. Flashing a radio that is S-OFF and actually setting the @ secuflag to S-off gives us 100% total access to every part of the phone and it's software, as it becomes network unlocked allowing you to use any SIM and also allows you to flash a ROM from any carrier (known as Super CID). It also makes it practically impossible to permanently loose root no matter what you flash. Once you have radio S-OFF, it makes it much easier to flash new HBoots and ROMs even if you flash something that is locked down tight.
Setting the Radio to S-Off is not necessary, and gaining S-OFF on the HBoot is more than most people will ever need. Radio S-Off is just the last step of the puzzle, but it is worth noting that you can permanently brick your phone if flashing a radio or a HBoot, if either of these go wrong you will end up with a shiny expensive paper weight so there is risk involved. If this helped you in any way then feel free to click on the thanks button. Meanwhile, happy hunting!
Sent from my C525c using XDA Premium 4 mobile app
To determine if you are S-OFF via HBoot or Radio you can do one of two things.
1: Go into fastboot and type
Code:
fastboot oem readsecureflag
If you get secure_flag with the number zero then congrats - you are radio S-Off
If you get secure_flag 3 then I am sorry, you are not radio S-Off. - your modded HBoot is ignoring the radio in regards to @ secureflag.
2: (I don't recommend this lol)
You can flash a stock HBoot and then reboot your bootloader. If you see S-On after already having S-Off then this means you were S-Off via HBoot. However, I would like to note that some HBoots are written out to prevent themselves from being over written so S-Off isn't lost, but this prevention does not always work and is usually patched by HTC relatively quickly.
Sent from my C525c using XDA Premium 4 mobile app
Another note... If you do not have radio S-Off then the following fastboot command will not work nor will it bring you back to S-On:
fastboot oem writesecureflag 3
Reason for this is because you are already S-On, but its being masked by your modded HBoot. So in this case, flash a stock HBoot and that will substitute for the failing command in fastboot
Sent from my C525c using XDA Premium 4 mobile app