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"
Related
Tried to run this on my HOX 1.82.502.3 and I get the follow error.
Restarting ADB
Pulling files
Checking if patch can be applied
Cannot patch. Token "[11111111]" must be either "[CWS___001] or [ROGER001]". Aborting! Your device was not altered.
Press any key to continue . . .
HELP!
Arie McD said:
Tried to run this on my HOX 1.82.502.3 and I get the follow error.
Restarting ADB
Pulling files
Checking if patch can be applied
Cannot patch. Token "[11111111]" must be either "[CWS___001] or [ROGER001]". Aborting! Your device was not altered.
Press any key to continue . . .
HELP!
Click to expand...
Click to collapse
Are you rooted? Also it would seem like you already have supercid. Since you don't match the two cids it says.
Sent from my HTC One X using xda premium
Yes I am rooted. How would I check for Super CID?
If I already have supercid, what would be my next step?
Just checked the bootloader and it still says locked.
Thanks
You could try to do bootloader unlock. If it works you do if it doesn't you don't. Not sure how to check.
Sent from my HTC One X using xda premium
I had a similar problem. I ended up patching the file manually. My CID was showing correctly CWS__001 starting at offset 214 so not sure what the issue was. To check if you have changed the CID try
Code:
adb reboot bootloader
wait for reboot then
Code:
fastboot oem readcid
It should read 11111111. If it does you can try
Code:
fastboot oem get_identifier_token
Leave the command prompt open and copy the text. You can find the exact instructions at htcdev.com in the unlock bootloader section by selecting other supported devices.
Arie McD said:
Yes I am rooted. How would I check for Super CID?
If I already have supercid, what would be my next step?
Just checked the bootloader and it still says locked.
Thanks
Click to expand...
Click to collapse
is your hox att or rogers....
if its neither then you need to flash the manual guide
Sent from my Galaxy Nexus using XDA
I have the AT&T version.
What software do I need to be able to do this?
Arie McD said:
What software do I need to be able to do this?
Click to expand...
Click to collapse
If you're on Windows you should download HTC Sync which will install the USB drivers for the phone. Then, uninstall HTC Sync which will still leave the USB drivers on your computer. Then download the Android SDK from here. Once you have that running you want to install "Android SDK Platform-tools" which should be near the top. Now you should be ready to run the commands, just open a command prompt and navigate to the directory the platform-tools were installed to.
On a side note, you can also check your CID by downloading CID Getter from the Play Store
Shweeeet ! Will try tonight and keep ya posted.
Since I am not familiar with SDK, is there a cheat sheet available? I have no idea where to start and how to fire this thing up.
Thanks
Thanks to all ! I had a Brain Fart. Completely overlooked the fact this is Linux until I saw the commands. Duh !
unlock bootloader
I'm having issues unlocking my bootloader. I go through all the steps, get to the end and cmd prompt says its sending unlock token (0 kb)... It will not go any farther than this. I have to then manually reboot. What am I doing wrong? I've searched the forums and cannot find an answer. Any advice would be appreciated. Thanks
Any ideas?
Sent from my HTC One X using XDA
I can't even re-unlock the bootloader for some reason either.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I mistakenly used the JBFW tool on my AT&T branded phone (CID: CWS__001) to change the CID to HTC__001, not realizing that my phone was still S-ON and the CID changing option was apparently for S-OFF only. I had root, I had the bootloader unlocked. Now I can't even get into recovery, and I think since my CID is apparently stuck as HTC__001, that the RUU for my phone's actual CID won't work. I should note that before I relocked the bootloader, I tried to change my CID back to the SuperCID but it would just freeze the phone. That's why I tried to relock it, hoping it would help. I thought I could just unlock it again, but it won't work. I can't flash anything via ADB, it all fails. This is the RUU I was trying to use:
RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio_0.19as.32.09.11_2_10.105.32.25L_release_271865_signed.exe
and I got a Wrong Customer ID error.
Is there anything I can do to remedy this situation or am I at the warranty center's mercy? Thank you in advance for any help.
im in the same boat, hopefully we get some help here soon, ive got another phone on the way from the warranty center but they want the one i have now and if they see its been tampered there gonna send me a bill for the full price of the phone. wish i could help.
We have the exact same phone. I have a dif RUU though. Mine says AT&T. I'll find the link to dl that RUU in a sec. Currently away from the pc where I have that page bookmarked
EDIT: I do believe that all the Cingular RUUs don't work anymore, their currently out of business thanks to our carrier AT&T... Don't know why you would try and use a Cingular RUU...
Sent from my HTC One XL using xda app-developers app
Myrder said:
We have the exact same phone. I have a dif RUU though. Mine says AT&T. I'll find the link to dl that RUU in a sec. Currently away from the pc where I have that page bookmarked
EDIT: I do believe that all the Cingular RUUs don't work anymore, their currently out of business thanks to our carrier AT&T... Don't know why you would try and use a Cingular RUU...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Cingular is att.
If you see a ruu that says.Cingular,it will work
Sent from my HTC One XL using xda app-developers app
Now, this is the correct RUU http://www.4shared.com/file/35bbU4_Y/htc_one_x_RUU_2205027_att_us_0.html. It's going to take anywhere from 10-25min to complete.
After you complete the RUU, go to this thread http://forum.xda-developers.com/showthread.php?t=1952426
Download and follow each step. You will then be rooted, correctly.
Myrder said:
Now, this is the correct RUU http://www.4shared.com/file/35bbU4_Y/htc_one_x_RUU_2205027_att_us_0.html. It's going to take anywhere from 10-25min to complete.
After you complete the RUU, go to this thread http://forum.xda-developers.com/showthread.php?t=1952426
Download and follow each step. You will then be rooted, correctly.
---------- Post added at 03:18 PM ---------- Previous post was at 03:16 PM ----------
Cingular doesn't have an RUU for the people that have 2.20, I've looked.
Click to expand...
Click to collapse
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I stand corrected.
Myrder said:
I stand corrected.
Click to expand...
Click to collapse
It's all good bro! You're trying to help,.that's all that matters. I've been trying to take a break from the Q&A and work on the unbricking. But something attracts me here :crying:
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
It's all good bro! You're trying to help,.that's all that matters. I've been trying to take a break from the Q&A and work on the unbricking. But something attracts me here :crying:
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I have a nag for wanting to help people and it seems you do too. Lol.
Speaking of, I've been trying to keep up with that thread you have. How's that coming?
he wont be able to flash the ruu because he changed his cid to the international one x to try to flash the international jb rom which would of bricked his phone if it worked. running "OUR" supercid might get it set to supercid and let you reflash ruu.
Lmao, now that is a hard pickle to get yourself into!!!
If cid was changed to HTC_001 properly, go snag a new token off htcdev website........I'm not going to explain the rest
Sent from my HTC One XL using Tapatalk 2
Just to let you know our (The HTC One XL). Super Cid is 1111111 (I'm pretty sure it's seven 1's?). In any case you should not be looking at the One X (Tegra) forums and much rather look at the One XL/ATT One X forums unless you enjoy staring at a $600 paperweight.
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
Just to let you know our (The HTC One XL). Super Cid is 1111111 (I'm pretty sure it's seven 1's?). In any case you should not be looking at the One X (Tegra) forums and much rather look at the One XL/ATT One X forums unless you enjoy staring at a $600 paperweight.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
8, I believe
First rfatmen
I wasn't able to change my CID back to the SuperCID via any method I could find. And I don't think the CID was "properly" changed/spoofed to HTC__001, but I definitely could still get verified tokens from HTCDev. The problem was that I couldn't re-unlock it by pushing the .bin via ADB because it just failed. Since I'd upgraded less than a week ago, I was able to convince the semi-clueless guy at AT&T to exchange my One X.
knyghtmayre said:
I wasn't able to change my CID back to the SuperCID via any method I could find. And I don't think the CID was "properly" changed/spoofed to HTC__001, but I definitely could still get verified tokens from HTCDev. The problem was that I couldn't re-unlock it by pushing the .bin via ADB because it just failed. Since I'd upgraded less than a week ago, I was able to convince the semi-clueless guy at AT&T to exchange my One X.
Click to expand...
Click to collapse
That's the spirit.
absolutelygrim said:
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
link to 2.20 ruu http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Crappyvate said:
link to 2.20 ruu http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Click to expand...
Click to collapse
well I know there is an RUU for it silly, I meant the naming convention isn't the same as previous RUU's
DvineLord said:
he wont be able to flash the ruu because he changed his cid to the international one x to try to flash the international jb rom which would of bricked his phone if it worked. running "OUR" supercid might get it set to supercid and let you reflash ruu.
Click to expand...
Click to collapse
I accidentally flashed recovery to boot portion. ie
HTML:
fastboot flash boot twrp.img
instead of
HTML:
fastboot flash recovery twrp.img
.
Then I also flashed recovery to recovery portion thinking that I can boot into recovery.
But now my phone boots and stays at twrp logo.
Even when I try to boot into recovery the same twrp logo nothing happens.
Hi, I am tryin last 2 days change root my phone, htc one x att. ON htcdev.com in the end I have this message "Error Code: 160. Error Reason: MID ..." so after that i read somewhere I have to change my CID. I try oneclick method- didnt work for me. what can I do know? thank you
mikailo said:
Hi, I am tryin last 2 days change root my phone, htc one x att. ON htcdev.com in the end I have this message "Error Code: 160. Error Reason: MID ..." so after that i read somewhere I have to change my CID. I try oneclick method- didnt work for me. what can I do know? thank you
Click to expand...
Click to collapse
Are you on the 3.18 jelly bean update?
I put a post on Androidcentral on how I did it:
http://forums.androidcentral.com/ht...x-after-ota-4-1-jelly-bean-update-3-18-a.html
but there is also this fourm on how to root: http://forum.xda-developers.com/showthread.php?t=1644167
and how to unlock bootloader: http://forum.xda-developers.com/showthread.php?t=1672284
and here is hasoon2000's all in one tool kit: http://forum.xda-developers.com/showthread.php?t=1952426
Search the forums. You're not the first person to ask this question, the answer is already in the forum. XDA rules: search before posting.
Sent from my Evita
I have thre 4.0.3 android version
htc sense 4.0
http://forum.xda-developers.com/showthread.php?t=1644167
http://forum.xda-developers.com/showthread.php?t=1672284
this 2 links I tried yesterday and didnt work for me
here you have to use htcdev.com- on the end of proces, I have error message " Error Code: 160. Error Reason: MID ..."
http://forum.xda-developers.com/showthread.php?t=1952426
I search a lot, and tried many methods..nothing work
Did you achieve supercid?
Sent from my One X using xda app-developers app
mikailo said:
I have thre 4.0.3 android version
htc sense 4.0
http://forum.xda-developers.com/showthread.php?t=1644167
http://forum.xda-developers.com/showthread.php?t=1672284
this 2 links I tried yesterday and didnt work for me
here you have to use htcdev.com- on the end of proces, I have error message " Error Code: 160. Error Reason: MID ..."
http://forum.xda-developers.com/showthread.php?t=1952426
I search a lot, and tried many methods..nothing work
Click to expand...
Click to collapse
Don't look at your Android version, you need to go by the HTC firmware version (1.73, 1.85, 2.20, etc.). Then use the corresponding (for your firmware version) root method on my Index: http://forum.xda-developers.com/showthread.php?t=1671237
The root method you linked is for firmware 1.73 only, which was the release version. So unless your One X is pretty old, this probably is not your firmware version. The SuperCID method you linked clearly states that you need to be rooted, which you are not. Therefore it won't work.
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?
Q&A for Super cid: 11111111
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Super cid: 11111111. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
marchetto said:
Hi, I've tried..I've doing all and it seems function, but when I restart bootloader cId isn't changed..why?! I'm so confused..
Please help me
Sent from my HTC One mini 2 using XDA Free mobile app
Click to expand...
Click to collapse
If you installed all OTAs, HTC introduced write protect in the latter ones. So, it appears that everything went smoothly, but the CID still remains the same. Try getting S-off first with rumrunner or moonshine and then use the write CID command to get supercid 11111111.
spikyshotgun said:
If you installed all OTAs, HTC introduced write protect in the latter ones. So, it appears that everything went smoothly, but the CID still remains the same. Try getting S-off first with rumrunner or moonshine and then use the write CID command to get supercid 11111111.
Click to expand...
Click to collapse
This is very old. I'm sure newer software prevents this from working. What software are you running
shootind5nukes said:
This is very old. I'm sure newer software prevents this from working. What software are you running
Click to expand...
Click to collapse
Facepalm S-OFF work pretty nice for HTC One S EU latest firmware. Rumrunner also works perfectly. Moonshine depends on firmware version.
shootind5nukes said:
This is very old. I'm sure newer software prevents this from working. What software are you running
Click to expand...
Click to collapse
I have T-mobile US phone. The issue I had with using Facepalm is that it requires you be SuperCID before using it. As @marchetto mentioned, the process used to go smoothly, but CID would still be the same. Moonshine didn't work for me either. Rumrunner did. So, had to first get S-off with that and then get SuperCID.
spikyshotgun said:
I have T-mobile US phone. The issue I had with using Facepalm is that it requires you be SuperCID before using it. As @marchetto mentioned, the process used to go smoothly, but CID would still be the same. Moonshine didn't work for me either. Rumrunner did. So, had to first get S-off with that and then get SuperCID.
Click to expand...
Click to collapse
I'm glad you got something to work.
Just execute... if you are S-Off
fastboot oem writecid 11111111
carlosjgp said:
fastboot oem writecid 11111111
Click to expand...
Click to collapse
Just tried "fastboot oem writecid 11111111" and I am s-off and it did NOTY change the CID- has anyone been able to do this?
Mine still says "BS_US002" - and I have the dev edition