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
Related
I've done a couple forum searches between the General & Q&A section, and I haven't found the answer.
I've already S-off'ed, Rooted, and flashed CWM 5.X. And I'm just wondering if Super CID is necessary after completing these steps.
I'm new to the Sensation/HTC products, so sorry if this is a really noob question.
U do because if u dont it will just limit the number of roms u can flash on ur phone for ex. i use insert coin
nd its based on European sensation nd If I have tmo cid I won't be able to use it
Sent from my HTC Sensation Z710e using XDA Premium App
deol 4ever said:
U do because if u dont it will just limit the number of roms u can flash on ur phone for ex. i use insert coin
nd its based on European sensation nd If I have tmo cid I won't be able to use it
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
That's not gonna happen. If you are s-off then you can install any custom rom you like.
I, for example, have Vodafone cid but i flashed insert coin, leedroid and rcmix so far.
You have to change cid only if you want to flash an official HTC RUU to, let's say, a Vodafone branded phone.
So for me Super CID is absolutely optional.
I am very confused about this.
I have not gone with SuperCID; I have CID=TMOB0101. I keep seeing in ROM descriptions "You must have SuperCID", and yet I succeed in installing and running that ROM without SuperCID.
I *am* S-OFF and rooted, of course, and I always make sure that I have the corresponding firmware installed.
I've installed current ROMs that are originating from several different continents, as far as I can tell.
So why do I keep being told that I need to go with SuperCID? It seems pointless.
varxx said:
I am very confused about this.
I have not gone with SuperCID; I have CID=TMOB0101. I keep seeing in ROM descriptions "You must have SuperCID", and yet I succeed in installing and running that ROM without SuperCID.
I *am* S-OFF and rooted, of course, and I always make sure that I have the corresponding firmware installed.
I've installed current ROMs that are originating from several different continents, as far as I can tell.
So why do I keep being told that I need to go with SuperCID? It seems pointless.
Click to expand...
Click to collapse
+1 I completely agree with you!...
SuperCID is optional, I think most people will do it as it will allow you to flash any firmware without having to worry if your CID is compatable with the firmware your trying to flash. For example with a vodafone CID you would really only be able to flash vodafone firmware. Although this doesn't cause an issue when flashing a ROM most devs will recommend a certain firmware to be used.
Saying that all the ICS based roms will require a firmware update so it would mean you would have to either edit files within the firmware, SuperCID and now for all those still to worried to SuperCID the guys over at the dev forum have made a nice sticky on firmware updates. HERE without the need to SuperCID
The CID would only limit the capability of flashing Stock Roms from different carriers, for example my CID is BM_001 which stands for Bell Mobile which is the original carrier of the device, if I were to flash a lets say Stock T-Mobile Rom I may encounter some issues. With Super Cid (which changes the CID to 1111111) you open your devices to all other "Carrier Roms"
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.
Hi folks,
I have unlocked and s-offd my Voda HTC Chacha.. installed a WWE Rom but havent recieved any OTA since then.. I am on 1.19 and there is a 1.54 OTA out..
just checked the CID through adb and its set to Super CID 11111111 instead of generic HTC__001. Tried changing it but I get Command Error. Any idea or solution for this?
Also, Is this the reason why no OTA are showing up?
If no, please advise how can I update the phone via OTA
Many thanks
What's your full version number? Afaik, 1.19 isn't a WWE ROM, it's Vodafone UK
qzfive said:
What's your full version number? Afaik, 1.19 isn't a WWE ROM, it's Vodafone UK
Click to expand...
Click to collapse
Here are the full details mate:
Android 2.3.3
Software 1.19.206.2
Baseband 47.14.35.3030h_7.47.35.17
Kernel 2.6.35.10-g8db500e
cheers
Searching "1.19.206.2" on Google brings me back to a thread here in XDA's Chacha section saying it's an O2 ROM - so you see any O2 apps or bootanimations? I've heard that O2 don't actually "brand" their Android phones with apps, but still make all updates go through them.
EDIT: Yup, 1.19.206.1/2 is an O2-UK ROM - I found this out from this forum thread: http://forum.gsmhosting.com/vbb/7588766-post44.html
RUU_Chacha_O2_UK_1.19.206.1_Radio_47.14.35.3030H_7 .47.35.17_release_195486_signed.exe
RUU_Chacha_O2_UK_1.19.206.2_Radio_47.14.35.3030H_7 .47.35.17_release_197936_signed.exe
As you can see, your software number refers to 1 of 2 O2 UK RUUs
You should flash the 1.33.401.1 RUU from this thread, then see if you get an OTA update to 1.52.401.1 - if not, try downloading it from this thread and apply it via stock Recovery, which is reported to work if you're S-OFF and have a correct CID (HTC__001 for example) or SuperCID.
qzfive said:
Searching "1.19.206.2" on Google brings me back to a thread here in XDA's Chacha section saying it's an O2 ROM - so you see any O2 apps or bootanimations? I've heard that O2 don't actually "brand" their Android phones with apps, but still make all updates go through them.
EDIT: Yup, 1.19.206.1/2 is an O2-UK ROM - I found this out from this forum thread: http://forum.gsmhosting.com/vbb/7588766-post44.html
RUU_Chacha_O2_UK_1.19.206.1_Radio_47.14.35.3030H_7 .47.35.17_release_195486_signed.exe
RUU_Chacha_O2_UK_1.19.206.2_Radio_47.14.35.3030H_7 .47.35.17_release_197936_signed.exe
As you can see, your software number refers to 1 of 2 O2 UK RUUs
You should flash the 1.33.401.1 RUU from this thread, then see if you get an OTA update to 1.52.401.1 - if not, try downloading it from this thread and apply it via stock Recovery, which is reported to work if you're S-OFF and have a correct CID (HTC__001 for example) or SuperCID.
Click to expand...
Click to collapse
Fantastic mate, downloaded it as we speak..
not sure how it stayed on 1.19 as after I used XTC Clip, the logos and boot image were gone so I assumed I had a stock rom.. oh well.. everyday is a learning day..
I will let you know how I get on..
cheers for your help mate..
Update... Installed the 1.33 which then took the OTA update which is all good... However I still can't change the CID to HTC__001.. (currently set at 1111111)
Sent from my HTC Sensation Z710e using Tapatalk
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
ajeevlal said:
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
Click to expand...
Click to collapse
I know but it doesn't help with OTA updates
Sent from my HTC Sensation Z710e using Tapatalk
ok, but..
ajeevlal said:
why you like to change the CID?
SUPER-CID (1111111) might have set during S-off thru xtc clip.... SUPER-CID (1111111) signifies you device is universal device, which enables to flash all languages/APN/other settings in your phone
Click to expand...
Click to collapse
True, but it forces non-qwerty keyboard users to manually modify the layout in /system/usr/
as described here , because CID is taken into account on default layout.
Once you know the trick, it's OK, but really annoying to do every time you install a new ROM
hey everyone, i had my telstra one xl on JB for awhile then i wanted to do the newest update from them so upon reading up on it i need to have supercid and s-off, so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111, sweet now to do s-off which failed to flash the RUU, i needed to relock the bootloader, so i relocked it.
problem is now its stuck in a bootloop to fastboot and wont show up in ADB devices, i also cant get into twrp in recovery now.
is there any way to fix this or throw the phone out?
It's a bit difficult to make out what you're saying in parts of that post.
Was s-off successful?
Was the RUU successful?
Which RUU did you use?
What are your current bootloader details?
Sent from my Evita
sirus17 said:
so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111,
Click to expand...
Click to collapse
Did you actually verify that you had SuperCID? I don't think there is a one-click for the Telstra version. The one-click app for SuperCID I'm aware of is intended for AT&T, and will fail with any other CID.
Which may actually be a good thing (if SuperCID failed). Since if a Jellybean RUU is flashed with SuperCID and s-on (its not clear whether you were successful with s-off) it will pretty much a guaranteed brick.
sirus17 said:
is there any way to fix this or throw the phone out?
Click to expand...
Click to collapse
If the screen comes on, its probably possible to recover. But we need more info as timmaaa indicated above.
There is actually a one-click tool for the Telstra version, I stumbled across it very soon after getting my phone mid last year. I found it on an Australian Android site, I think it was Ausdroid.
I'm not sure whether the tool is specifically for the Telstra version alone, but it definitely works on Telstra Evitas as I used it on my fiance's Evita (and mine which is a Hong Kong model).
Sent from my Evita
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
twistedddx said:
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
Click to expand...
Click to collapse
Really not sure, now that I look into it more. If its the old one by DesignGears, it does work with Rogers, but doesn't seem to mention Telstra (at least if I just search the thread for "Telstra"): http://forum.xda-developers.com/showthread.php?t=1672284
And x-factor also fails for any CID except AT&T, if I understand correctly. So it seems these scripts all look for certain CIDs, so if its not explicitly included, they will fail. Of course, if there is one made specifically for Telstra (as timmaaa mentioned) it apparently wasn't posted on XDA.
But really my main point is that the OP needs to verify and be clear on this, as well as several other factors.
I was wondering if someone could help me? ... I recently acquired a Telstra Htc One XL and am having troubles trying to update.
Current stats
android 4.1.1
sense 4+
software 3.17.841.2
EVITA PVT SHIP S-OFF RL
*****locked*****
CID-11111111
HBOOT 2.14.0000
RADIO- 0.23a.32.09.29
I'm 99.9% sure most testra one xl's are up to 4.2.2 with sense 5 which is i think two updates in front of mine
can anyone shed some light on my situation?
When you say you're having trouble updating what exactly do you mean?
Sent from my Evita
When i "Check for Updates" it tell me that there are no more updates.... when Im sure there are another two...
Are you in Australia?
Sent from my Evita
Sure am ... Good old city of churches" Adelaide" ..
timmaaa said:
Are you in Australia?
Sent from my Evita
Click to expand...
Click to collapse
His profile says he is
Yeah, but still needed to check. Have you thought about re-unlocking your bootloader? It's been modified in the past which might have something to do with your update problem. If you unlock your bootloader you'll be able to install a custom recovery and then you can install whatever ROM you like. We have the stock Telstra Sense 5 Android 4.2.2 ROM in our development section. We also have a few other Sense 5 ROMs to choose from, ranging from stock to tweaked.
Sent from my Evita
The thing is that it hasnt been messed with.I got the phone from a HTC rep that i know ... he had it in his draw for over six months ...I just wanted the stock update but maybe rooting might be the easier way
It definitely has been messed with, phones that are s-off and have SuperCID don't come out of the factory like that. Somewhere along the way someone has done those alterations to the device.
There is just one problem I've realised, your phone has a SuperCID of 11111111 which has been blocked by htcdev. You're s-off though so you can actually change that as many times as you like using fastboot. If you want to unlock your phone you'll need to change it to 22222222 using the following fastboot command:
Code:
fastboot oem writecid 22222222
You can then check the new CID by using this command:
Code:
fastboot oem readcid
Once that's done you can go to htcdev and go through with the unlock bootloader process.
In order to do the above process you will need to install adb/fastboot and HTC drivers.
Sent from my Evita
No problem ... thanks for that ....I have rooted my one x before HTC_023 fairly basic but my mate swears that the phone came straight from HTC as a Tell us what you think before we send you more kind of thing .. Cheers for the info ...
Actually one more thing ... is it possible to do a RUU update with this to 4.2.2?
There is no RUU for 4.2.2, the only way is to run an earlier RUU and take OTA updates to get there. Since you can't get the OTA I guess that isn't an option though.
Sent from my Evita
grekojim said:
Sure am ... Good old city of churches" Adelaide" ..
Click to expand...
Click to collapse
Within 30 minutes drive from me no doubt
Supercid and s-off from factory or not still means you are off the official path.
Things I might do:
fastboot oem writecid TELST001
Then try the OTA again
or
RUU back to 1.89.841.9 as a RUU exists for that, then ota forwards to 5.06.841.1
or
Unlock bootloader
Flash Turges 5.08 firmware zip and then take one of the Sense 5 ROMs. There is a stock Telstra ROM even.
PS nag the HTC rep for a more recent RUU, eg 2.40.841.4, 3.17.841.2, 3.17.841.9 or 5.06.841.1 and share with us
---------- Post added at 12:56 PM ---------- Previous post was at 12:48 PM ----------
timmaaa said:
Once that's done you can go to htcdev and go through with the unlock bootloader process.
Click to expand...
Click to collapse
He has s-off does he need a token or even need to unlock at all?
I have often wondered the same thing, but I've been assuming that in order to flash TWRP recovery you need an unlocked bootloader.
It's nice to see a few Aussies on here by the way, I'm in Melbourne myself.
Sent from my Evita
great ... trying the cid thing first ...
My phone from an att employee came s-off and with a locked boot loader as well. It just looks like that's how HTC and att do it.
Sent from my HTC One XL
Alright cid change didnt work ..now to find the 1.89.841.9 RUU
Click the link in my signature, from there you'll find a link to the HTC RUU thread.
Sent from my Evita
RUU links all changed and the index doesnt keep good track of the current RUU sites.
Try:
http://www.androidruu.com/?developer=Evita
http://www.androidruu.com/getdownlo...09.01_10.93a.32.20L_release_266699_signed.exe
Thank you heaps .....
Just in case .. i got the unlock code from htc deV But when my cid was 11111111 .....would that matter if i use that code now that my cis is telst001?