Related
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
chuaniyang said:
Hey, All
I was successful unlock , root following this thread,
http://forum.xda-developers.com/showthread.php?t=1583427
Then I'm trying to install this RUU , RUU_Ville_U_Rogers_WWE_1.70.631.1
this step always get device id error,
so I back to stock recovery, modify CID form "HTC__203" to "11111111", and relock with following this thread,
http://forum.xda-developers.com/showthread.php?t=1674202
Yes, finally "RUU_Ville_U_Rogers_WWE_1.70.631.1" installed, all function works.
Now, I have a problem , I'm trying to unlock again, so i using "faseboot oem get_identifier_token", and paste id to htcdev step 11, and get a new "Unlock_code.bin"
when I using this "Unlock_code.bin" to unlock my device, everything seems normal, but when I reboot, the device still display RELOCKED
any suggestion?
Click to expand...
Click to collapse
Well it's still gonna show relocked if that's what your talking about bcuz you unlocked it then relocked so it isn't gonna show tampered with unlocked at the bottom that's only for the first time you unlock it that it says tampered with unlocked at the bottom, but if you unlock it again it's just gonna say relocked not unlocked. Hopefully this answers your question.
Sent from my samsung galaxy player
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
chuaniyang said:
my screen didn't have "tampered" any more. I'm not sure but it's strange.
so, I post the photo step by step what am i do. see 001.jpg ~ 009.jpg with following link
https://www.dropbox.com/sh/ksyrdgvjo4xrgiw/1Kr3CmwHnd
Click to expand...
Click to collapse
Yea that is strange but I don't think it would be considered a problem unless you have the phone stuck in Bootloop or something strange is going on with the phone like apps.not working or battery draining fast. I can see what your worried about and it is strange but I wouldn't worry too much about it but you should look up somewhere in the forums about that but I wouldn't know much about the international version I'm on the US version. Good luck with your problem
Sent from my samsung galaxy player
I checked this thread
http://forum.xda-developers.com/showthread.php?t=1671643
seems I need to wait someone can S-OFF this device
superCID can install any RUU, but can't unlock, root, install custom ROM without S-OFF
I've managed to change my cid and install a new Rom then unlock it and root so it's possible
Sent from my HTC One S using Tapatalk 2
the other reason maybe user just can unlock/relock limited times. ?
does any one change CID and unlock/relock over 3 times ?
I've relocked about 4 time's now changed cid once
Sent from my HTC One S using Tapatalk 2
My default cid is HTC_203, i changed to HTC__102, HTC__001 and 11111111.
Everytime cid changed, I will lock/unlock again. When changed to 11111111, I can't unlock anymore.
Sent from my HTC VLE_U using xda app-developers app
Mate, the CID is in the partition that gets summarized together with the other partitions when calculating the Unlock Token.
So, if you change this or any other relevant partition by for example changing the CID, you will invalidate your old unlock token.
After changing CID, please re-lock bootloader, then go "fastboot oem get_identifier_token" and go to HTC-Dev and unlock again.
After that, you can proceed with everything else as usual.
If you cannot unlock with CID 11111111 this is NOT normal. Everyone else can.
So either you did something wrong in the above process or you somehow half-bricked your phone.
Yes, everytime I changed cid, I got a new unlock code. if not, fastboot will give me error message during unlock process.
I think my situation is not normal, and I'm trying to find out why then fix it. Now, I still can install any RUU , if they have the same HBOOT version.
Sent from my HTC VLE_U using xda app-developers app
I'd guess it's a half brick because if you can't unlock something is wrong. There is no unlock counter because no-one has had it yet. I've unlocked about four or five times now too and don't have that problem. You should consider sending it in for repair. As long as there's no S-OFF you'll have no chance to force an unlock I guess. If the security is as complex as on the HOX, it's likely the situation couldn't even be resolved by a jtag programmer or such.
sent from the tip of my finger
Thanks, no one have the same question as me. I will try to call HTC service.
CID 11111111 Issue
Hello there,
I want to install an older RUU (actually installed is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed )
my intention is to downgrade the Basbeand Version with this Procedure to get rid of this "HomeButton-Jumparound-Whatever" Issue which occures when i am in GSM (2G) Mode.
when i get this phone brandnew there was no Problem, just after updating to 1.78 this ****** began.
When i changed my CID from HTC__102 to 11111111 the first time everything went fine and i was able to install every RUU
Now i tried to change my Radio to an older Version by install an older RUU, but it won't work no more, i allways get an Error 140 or 131.
if there is another method to change the radio version, I'd appreciate any council
relock Bootloader, turn off virus scanners, run ruu as admistrator, I've done of course
I would be grateful for any help
ERROR 140 : bootloader error
ERROR 131 : cid error
are you install T-MOBILE 1.84 RUU ?
this will chane HBOOT version from 1.08 to 1.09
if you can unlock, try to find some way change your HBOOT version back to 1.08.
then you can insall RUU_Ville_U_HTC_Europe_1.78.401.2.
RUU_Ville_U_HTC_Europe_1.78.401.2 can be installed only with the other it does not work
i've got HBOOT 1.13.000 (shown in bootloader)
i just want to downgrade the Radio..
edit: when try to install RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed
or
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed
i get Error 155
we have some thing different. but you are lucky then me. I just can install T-MOBILE 1.84 RUU, if I try to install another version. always got HBOOT version error
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-main: 1.84.531.2
(bootloader) commitno-bootloader: e964c535
The HTC srevice center(tw) call back. they say they find some motherboard error on my device.
I don't think change cid and unlock will cause it happen.
My CID is 22222222, even though I RUU'd back to 1.85. My Hboot 1.09, and my phone is S-Off'd.
Why is it showing as 2222222? I've flashed other HOXs before and never experienced this issue.
Can't you just
(Fastboot oem writecid 11111111) ?
Try that in bootloader/fastboot.
Sent from my HOX w/CM10.1 4.2.2 s-off
Actually OP...better question is why you want 11111111?
22222222 i used that and got SuperCID because i read that HTC closed the 11111111 loophole in its unlocking process (if you wanted to go S-OFF.
Supercid is not a loophole, it was designed and implemented by Htc to do exactly what it does, to make a device not locked by region checks.
twistedddx said:
Supercid is not a loophole, it was designed and implemented by Htc to do exactly what it does, to make a device not locked by region checks.
Click to expand...
Click to collapse
But it was probably never intended for the general public to use. Evidenced by the fact that HTC started blocking it in HTCDev.com bootloader unlock process. So in that sense, it was a loophole that was closed.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
Deus_eps_machina said:
Actually OP...better question is why you want 11111111?
Click to expand...
Click to collapse
+1 to that. There is no purpose to changing it to 11111111, and no benefit to it (especially if you are S-off).
theking_13 said:
Why is it showing as 2222222? I've flashed other HOXs before and never experienced this issue.
Click to expand...
Click to collapse
If your CID is 22222222, you must have made it so. Or the person who owned the phone before you, if you obtained it used.
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
theking_13 said:
My CID is 22222222, even though I RUU'd back to 1.85.
Click to expand...
Click to collapse
RUU will not change CID, by design.
I'm sending my phone to T-Mobile and getting a new one via handset warranty. The volume buttons broke off and I can't handle the reboots anymore so T-Mobile said I can get a new one. They told me that I have to return it to completely stock though or else I will be charge $98.
I'm currently running HyperSensation. How do I go about returning it completely to stock so I don't get stuck with this charge?
ImHuge07 said:
I'm sending my phone to T-Mobile and getting a new one via handset warranty. The volume buttons broke off and I can't handle the reboots anymore so T-Mobile said I can get a new one. They told me that I have to return it to completely stock though or else I will be charge $98.
I'm currently running HyperSensation. How do I go about returning it completely to stock so I don't get stuck with this charge?
Click to expand...
Click to collapse
Hi,
Run a RUU.
Look HERE
malybru said:
Hi,
Run a RUU.
Look HERE
Click to expand...
Click to collapse
Thanks!
I did super cid when I rooted. Will I need to change that back to its normal value before sending it in? How do I find which value to change it to?
ImHuge07 said:
Thanks!
I did super cid when I rooted. Will I need to change that back to its normal value before sending it in? How do I find which value to change it to?
Click to expand...
Click to collapse
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
To get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place of the 11111111. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Yours is likely to be
T_MOB010
malybru said:
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
To get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place of the 11111111. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Yours is likely to be
T_MOB010
Click to expand...
Click to collapse
Ah thank you. I have no idea if I need to get S-ON or supercid back to normal or not. I have the handset protection plan so they sent me a new one and I'm sending mine in and the rep at the store said make sure there is no trace of rooting or they will charge me $100. I don't know if that just means the RUU or if they will check for S-ON or supercid. Does anyone know?
Another question. If I can't figure out how to get it back to stock then should I just brick it and send it back? Will they be able to tell that it bricked due to rooting?
ImHuge07 said:
Ah thank you. I have no idea if I need to get S-ON or supercid back to normal or not. I have the handset protection plan so they sent me a new one and I'm sending mine in and the rep at the store said make sure there is no trace of rooting or they will charge me $100. I don't know if that just means the RUU or if they will check for S-ON or supercid. Does anyone know?
Click to expand...
Click to collapse
Hi,
What the rep said ,means you have to remove supercid and return to s-on.
This has all been explained in the threads I gave you.
ImHuge07 said:
Another question. If I can't figure out how to get it back to stock then should I just brick it and send it back? Will they be able to tell that it bricked due to rooting?
Click to expand...
Click to collapse
Hi,
If during the process of returning it to stock,the phone gets bricked,then,they could not tell what has happened.
malybru said:
Hi,
What the rep said ,means you have to remove supercid and return to s-on.
This has all been explained in the threads I gave you.
Hi,
If during the process of returning it to stock,the phone gets bricked,then,they could not tell what has happened.
Click to expand...
Click to collapse
Perfect.
Do I have to change the radio at all do you think? Or is it included in the RUU? And what about the kernel? I assume that's in the RUU as well?
malybru said:
Hi,
They said they want it completely stock,which is what a RUU will do.
It says nothing about removing supercid,or returning to s-on.
If you wanted to remove supercid,then,follow this:
To get your CID back to stock, do the following:
Connect to ADB, run "adb reboot-bootloader"
Then enter the command "fastboot oem writecid 11111111", except put your carriers CID in place of the 11111111. If you do not know your CID, refer to this thread http://forum.xda-developers.com/showthread.php?t=1195475
Then run "fastboot reboot-bootloader" and then "fastboot getvar cid" to verify it successfully changed.
Yours is likely to be
T_MOB010
Click to expand...
Click to collapse
Last question, and thank you very much for the help so far.
Right now I have supercid so should I change back to T_MOBO10 first before doing all the steps on the RUU up there or can I do it after?
And also how do I tell if my boot loader is locked or not? Following the instructions on the RUU I'm S-OFF but I'm not sure if the bootloader is locked or not. I don't see unlocked anywhere so should I assume its locked?
ImHuge07 said:
Perfect.
Do I have to change the radio at all do you think? Or is it included in the RUU? And what about the kernel? I assume that's in the RUU as well?
Click to expand...
Click to collapse
Hi,
Radio and kernel are included in the RUU
ImHuge07 said:
Last question, and thank you very much for the help so far.
Right now I have supercid so should I change back to T_MOBO10 first before doing all the steps on the RUU up there or can I do it after?
And also how do I tell if my boot loader is locked or not? Following the instructions on the RUU I'm S-OFF but I'm not sure if the bootloader is locked or not. I don't see unlocked anywhere so should I assume its locked?
Click to expand...
Click to collapse
Hi,
I would change the cid,run the RUU,and then s-on.
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?
I've tried to unlock the bootloader for my HTC One X multiple times but every time it's failed, I keep getting the same error on HTC Dev
"We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 160.
Error Reason: MID Not Allowed."
Any Help?
You have to have superCID first.
Use this: http://forum.xda-developers.com/showthread.php?t=2283760
Sent from my One Xl using xda premium
magnetboard said:
You have to have superCID first.
Use this: http://forum.xda-developers.com/showthread.php?t=2283760
Sent from my One Xl using xda premium
Click to expand...
Click to collapse
I tried this method and double-clicked the "Only One X" file and it failed to put my CID at 11111111 it stayed at CWS__001
Try doing the steps by yourself. Usually doing it that way will work better
Sent from my One Xl using xda premium
magnetboard said:
Try doing the steps by yourself. Usually doing it that way will work better
Sent from my One Xl using xda premium
Click to expand...
Click to collapse
How would I go about this?
Look at the first post of that page. It has all of the commands.
Sent from my One Xl using xda premium
Hang on, that might not even be the right method depending on his current firmware.
@frozen23
I need to see your bootloader details please, then I can direct you to the right method.
Sent from my Evita
See the FAQ thread sticky at the top of this section, and look at Question 5. Find the correct root/bootloader unlock method for your current firmware.
They call them "frequently asked questions" for a reason".
I assume you mean the lines of text at the top of the bootloader screen, so here
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.18.0000
RADIO -1.35A.32.45.27
OpenDSP-c33.1.0.45.1128
eMMC-boot
Dec 3 2013, 17:10:01:-1
HBOOT
There's no method for your specific firmware, the last known method might work though. Here it is:
http://forum.xda-developers.com/showthread.php?t=2285086
Give that a try. If it doesn't work it means they've plugged the "hole" so to speak, and you'll have to wait for a new exploit to be found.
Sent from my Evita
If this method dosen't work is there a way to perhaps downgrade to a firmware where I can root it?
No there isn't, otherwise everyone that came before you world have done that. If it doesn't work there's nothing you can do except wait for a senior dev to find a crack.
Sent from my Evita
Ok Thanks for all of the help I'll try out this method
Btw is there a windows version of this root method?
It is Windows compatible. Check out my q&a thread (link in my signature), I wrote a quick guide of that method for someone in the last few pages.
Sent from my Evita
I tried using your guide and when I executed one of the adb shell commands I got this error
"adb shell ln -s /data/local/tmp/busybox /data/local/tmp/sed link failed File exists"
Can you please check your CID?
Code:
fastboot oem readcid
Sent from my Evita
Yea sure it's CWS__001 isn't it suppose to be "11111111"?
Did you use the fastboot command to get your CID?
Sent from my Evita
Yes I did
"C:\sdk>fastboot oem readcid
...
(bootloader) cid: CWS__001
OKAY [ 0.010s]
finished. total time: 0.010s"