Hi ,
Wanting to get rid of 3 uk junk and flash to normal UK RUU
Do we need super CID?
My bootloader is unlocked , can't download the RUU from from the Dev section as all the slots are gone , or when it seems to work it errors out .
Has anyone got the latest UK RUU file they can share with me and can someone confirm if I need Super CID to run RUU to unbrand
Thanks in Advance
Just flash Modaco or the Virtuous roms through recovery, these are unbranded and really good.
You will need to flash a Recovery image first though.
Hi and thanks
Yes , I understand this but I want to just unbrand through RUU then re-lock my bootloader.
Do we need Super CID ?
Ok can someone remind me if I need S-Off to change the CID , playing around with ADB at the moment
If Im honest mate, no idea what you mean by CID...
But if you want a new rom, all that needs to be done is unlock bootloader, flash recovery, flash rom.
Thats all anyone has done in the dev threads, and worked fine for me (coming from a retail, unbranded unit).
You can 'lock' the bootloader again, BUT it never goes back to its true original state. This is as HTC designed their unlocking/locking process to be (and is stated in their terms when you go to their site to unlock).
Edit: OK, just read up on it. Possibly then! Depends how annoying 3 are I suppose... Probably best to ask one of the devs
Edit 2: CHeck the following, may be of help (though its for the One X)
http://forum.xda-developers.com/showthread.php?t=1594262
http://android.modaco.com/topic/353106-debrand-one-x/
Edit 3: If you're applying a flashable zip, does the CID limitiation on RUUs even come into play?
Hi thanks ,
Yea what I want to achieve is this .
My CID is HG3____001 this will need to be changed to a CID that is HTC UK specific usually HTC_____001
To find out your CID in ADB
Fastboot Getvar CID
To get to a retail version from a branded version , what usually needed to happen was this .
Unlock bootloader , change CID to 11111111 via ADB
Run the specific UK RUU.exe
Change your CID to the HTC_____001 which is the usual default for UK unbranded devices .
re-lock your bootloader and then you should receive OTA updates from HTC instead of your network supplier which can take months
I can't remember if S-off was needed to do this. I have just checked revolution site and One s is not listed , will play around tonight though and see
Thanks for the help so far
Hi, I know what CID is - coming from the Sensation.
I dont think its possible to change CID without S-OFF, you cant use advanced ADB functions with S-ON
Until revolutionary or someone else makes tool for S-OFF, we will just have to stick with HTCDev, Its not the best, but it allows to flash recovery and ROMs so its better than nothing.
Im pretty sure there will be some progress in the next few weeks, Once the phone is available worldwide
Ahh ok , thanks , yea this phone is set S- on , so S-off will be needed sooner or later
yeah, as development develops and more rights are needed from the phone, S-0FF will eventually be a MUST.
I wish it was available already, I hate the fact that HTC know i have tampered with my HBOOT and voided my warranty.
Luckily enough, if i have a problem, my provider fixes / repairs the phone, Not HTC, So i might just get off lightly
I think HTC will know if you have tampered with the phone period if they wish to look that far into it .
Unless you fry your processor where you have set it too high etc then shouldn't be a problem. If you have a hardware problem such as your screen fails , battery etc then should be fine .
As you say though , if you brought it through a retail unit then that is where it is returned so in some respects is a bit easier as they will use a third party repairer acting for HTC .
well with the sensation it was possible to return everything back to stock, Including the bootloader and S-ON..
There was no way it could be diagnosed as being tampered with, If you did it properly..
But with HTCDev. youve already submitted a code (which i assume contains serial number) so all they have to do is check whether that device matches anything on their database of tampered devices. Thats why i dislike it so much..
But i need root for most of my apps so there was no workaround for me...
I see on the One X forum S-off is under way . Can't wait to get this baby to true stock.
Just did another Google search for S-Off on the S but nothing as yet .
hello everyone i just recieved an htc sensation as an insurance phone since my g2x stopped working . i loved that phone and it was super fast but this is all t-mobile said they could give me. Anyways i have it and now i wanna flash different roms lol.
So i went through the process of getting the code from htcdev.com and unlocking the bootloader. But now when i try and root it from the "HTC All in One Rooting Tool Kit" using the one_x program, it doesnt work. It lets me reboot into recovery but then when i click on the root button and press enter in cmd box all it says is device not found or something like that. So my question is, is when its in bootloader can the computer still recognize the phone from the usb cord or is there something else i should do first?
think i have the same problem
hey, just got my brand new htc today, i have been able to unlock my bootloader via htcdev, all went well....but s-on my hboot is 1.27.0000 which is the issue!!!
from what i have found currently revolutionary method for s-off isnt currently supported.....
i have ICS installed 4.0.3, dam you carphonewarehouse lol
still searching and looking, does anyway have any further info, how to s-off,ROOT, or install a custom rom? or do i just have ti wait???
hi everyone,
Sorry if I posted this in the wrong forum. I have the One X which I just rooted, unlocked BL and also did S-off just over the weekend as I was wanted to try some JB. Now my sim card slot failed, it keeps saying no sim card found. I tried my sim on a different phone and the sim works. Now I am trying to get back everything as close to stock(2.20) as possible, so that I can get a exchange with att/htc. I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ? I still have s-off, Is there anyway I can go back to s-on and reset my c-id ?
Thanks in advance.
Just to elaborate on my original message below, though I have s-off, and unlocked bootloader, I have not flashed any ROM. I just flashed the twrp recovery.
Now I have everything back to original but for the following
a) I am still S-off. Can I go S-On ?
b) bootloader says relocked, can I make it to say locked ?
c) can someone point me to the link for 2.20 RUU zip file ?
Thanks,
onex_001 said:
hi everyone,
Sorry if I posted this in the wrong forum. I have the One X which I just rooted, unlocked BL and also did S-off just over the weekend as I was wanted to try some JB. Now my sim card slot failed, it keeps saying no sim card found. I tried my sim on a different phone and the sim works. Now I am trying to get back everything as close to stock(2.20) as possible, so that I can get a exchange with att/htc. I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ? I still have s-off, Is there anyway I can go back to s-on and reset my c-id ?
Thanks in advance.
Click to expand...
Click to collapse
onex_001 said:
I tried to relock the bootloader and it worked but it says relocked on the top. I read somewhere that going back to s-on would reset the relocked flag to just locked ?
Click to expand...
Click to collapse
No, you've got it backwards. Its intended to say RELOCKED (or UNLOCKED) once its been unlocked. It might be possible to change these flags, if you have S-Off. But such a thing has not been discovered yet. Nor has a method to S-on been discovered yet (or at least not that has been posted here).
Just relock and RUU. It will still say RELOCKED and S-Off, (otherwise stock). But AT&T doesn't seem to care about the bootloader being unlocked on this device. Many people have gotten warranty service from AT&T for phones that say RELOCKED. I think some folks have even warrantied devices UNLOCKED and running custom ROMs! Just make sure you go through AT&T, as HTC themselves are known to be much more strict about their warranty coverage.
---------- Post added at 04:46 PM ---------- Previous post was at 04:42 PM ----------
onex_001 said:
c) can someone point me to the link for 2.20 RUU zip file ?
Click to expand...
Click to collapse
Don't know why people ignore this, and make life so hard for themselves:
http://forum.xda-developers.com/showthread.php?t=1671237
You can also get it straight from HTC's support website.
Going back to S-on is simple fastboot command, but there's no reason to do it.
You can edit some of your bootloader text in various ways. Start with this thread:
http://forum.xda-developers.com/showthread.php?t=2156368
But don't try any of this unless you know what you're doing.
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.