Related
Can someone help me out? Im trying to unlock my bootloader on my one x and when I go to submit the unlock token on htcdev, it keeps failing and will never go through. Does anyone know a way around it? A different way of unlocking the bootloader? I would really appreciate it if I can get some help with this.
Thanks in advance
iLToRReNT said:
Can someone help me out? Im trying to unlock my bootloader on my one x and when I go to submit the unlock token on htcdev, it keeps failing and will never go through. Does anyone know a way around it? A different way of unlocking the bootloader? I would really appreciate it if I can get some help with this.
Thanks in advance
Click to expand...
Click to collapse
Its a real pain in the ass. What I did is cut and paste the key into a text editor. You have to remove leading spaces from the top make sure you include the lines that have the >>> on the top and the bottom. Make sure the numbers all line up it's a ***** to get right.
Thanks, I'll give it a shot and post back if it works.
gunnyman said:
Its a real pain in the ass. What I did is cut and paste the key into a text editor. You have to remove leading spaces from the top make sure you include the lines that have the >>> on the top and the bottom. Make sure the numbers all line up it's a ***** to get right.
Click to expand...
Click to collapse
Not quite sure I understood what you said, and if I did, I did it wrong. Do you think i could send you the token and you do what is needed? Then you could send it back to me. I don't mean to be a bother about it.
Sorry no can do. I'm on vacation no computer.
gunnyman said:
Sorry no can do. I'm on vacation no computer.
Click to expand...
Click to collapse
Ok well thanks anyways.
Did you manage to get it? PM me your token if you still need help and i'll take a quick look at it.
I have the same issue.. Mine says it's too long.. It's a pain in the ass..
Sent from my HTC One X using xda premium
iLToRReNT said:
Can someone help me out? Im trying to unlock my bootloader on my one x and when I go to submit the unlock token on htcdev, it keeps failing and will never go through. Does anyone know a way around it? A different way of unlocking the bootloader? I would really appreciate it if I can get some help with this.
Thanks in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1709424
Follow these instructions. Only works on 1.85
I know what you're talking about there. I made sure I right-clicked on the first < on the line to mark. THen, clicked where I marked exactly to select. Cntrl C, Cntrl V and it works. I know it's a PITA...took me a few tries before I got it.
Still a problem
subarudroid said:
http://forum.xda-developers.com/showthread.php?t=1709424
Follow these instructions. Only works on 1.85
Click to expand...
Click to collapse
Yeah that's another one of my problems, I'm on 2.20, which is not root capable . Do you know a way of downgrading to 1.85?
iLToRReNT said:
Yeah that's another one of my problems, I'm on 2.20, which is not root capable . Do you know a way of downgrading to 1.85?
Click to expand...
Click to collapse
Wait your on 2.20...... You can't root or unlock your bootloader because you need root to change your cid so that you can unlock your bootloader from HTC dev. There is no current exploit to root 2.20 unless you were already unlocked prior to the update. You re going to have to sit tight till someone comes up with a new exploit for 2.20.
Sent from my Nocturnalized Beast
...
E.Cadro said:
Wait your on 2.20...... You can't root or unlock your bootloader because you need root to change your cid so that you can unlock your bootloader from HTC dev. There is no current exploit to root 2.20 unless you were already unlocked prior to the update. You re going to have to sit tight till someone comes up with a new exploit for 2.20.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Yeah, that's why I was wondering if anyone knew a way of downgrading. I posted this thread before I found out that you root before unlocking bootloader on this phone. I thought that just running a 1.85 RUU would downgrade it but that failed. So do you have a way of downgrading?
There's no way to downgrade either.
...
gunnyman said:
There's no way to downgrade either.
Click to expand...
Click to collapse
FUUUUCK! Well thanks for any information you people gave me.
Hi all,
I was hoping I could get updated on the lastest as I just recieved an AT&T One X and I am also on 2.20...Have we had any progress toward Root or Unlocking the Bootloader?
Appreciate any information you may have?
maddie01 said:
Hi all,
I was hoping I could get updated on the lastest as I just recieved an AT&T One X and I am also on 2.20...Have we had any progress toward Root or Unlocking the Bootloader?
Appreciate any information you may have?
Click to expand...
Click to collapse
Just go over the the 2.20 root think tank thread, instead of digging up a 2 month old thread.
I was flashing a new rom and it failed so i couldnt do anything except flash 2.20 back on my phone again. But prior to having 2.20 i had unlocked my phone so i know my token works and i have done it before but when i try to use my token now it gives me a signature error. Can anyone help me get my phone unlocked? My CID is 111111111.
Thanks in advance
leighton1245 said:
I was flashing a new rom and it failed so i couldnt do anything except flash 2.20 back on my phone again. But prior to having 2.20 i had unlocked my phone so i know my token works and i have done it before but when i try to use my token now it gives me a signature error. Can anyone help me get my phone unlocked? My CID is 111111111.
Thanks in advance
Click to expand...
Click to collapse
Nvm i figured it out finally i just had to resubmit for a token that would work with the 2.20 update.
Unlock that bad boy, push twrp and start flashing roms!
does getting a new token after 2.20 update make it stick easier?
No, as long as the token is accepted, it doesn't matter. It's weird that they can be finicky as far as actually unlocking it goes. Id like to learn more on its full process of how it actually initiates, when the actual unlock happens, where its sent...but there's a lot I want to know lol, add it to my before I die list I suppose
Sent from my HTC One XL using Tapatalk 2
DvineLord said:
does getting a new token after 2.20 update make it stick easier?
Click to expand...
Click to collapse
My 1.85 Unlock_code wouldnt work with 2.20, but now i cant get my phone to take a 4.1.2 ROM gets stuck on the boot so idk i thought it was something i did last night.
18th.abn said:
No, as long as the token is accepted, it doesn't matter. It's weird that they can be finicky as far as actually unlocking it goes. Id like to learn more on its full process of how it actually initiates, when the actual unlock happens, where its sent...but there's a lot I want to know lol, add it to my before I die list I suppose
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Maybe the unlock token is a different size for the different versions like 1.73, 1.85 and 2.20? idk. I do know that it seems to work almost like a software activation key.
leighton1245 said:
My 1.85 Unlock_code wouldnt work with 2.20, but now i cant get my phone to take a 4.1.2 ROM gets stuck on the boot so idk i thought it was something i did last night.
Click to expand...
Click to collapse
You have to flash the boot.img separately with 2.20 through fast boot. Fastboot flash boot boot.img
Sent from my One X using Tapatalk 2
ComposMentis said:
You have to flash the boot.img separately with 2.20 through fast boot. Fastboot flash boot boot.img
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Awesome thank you
ok like the title says ive been messing with this thing for a week now and im getting to the point im about to smash it with a hammer
its stuck in a boot loop and i have no backup to load apparently. it was rooted when i got it and my roomate messed it up while i was at work im not sure how or what was done but no matter what i try to do i cant get it out of this loop. im not familiar with android at all ive been reading and searching but i cant find anything helpful ive tried to ruu a few times not really knowing which files to use i finally found out that the radio needed to be the same found a matching file but still no luck i know im gonna get flamed for being so uneducated in this matter but i have indeed searched and i feel im left with no other option then to ask for assistance here
i can get to the boot loader and im just going to type down exactly what i see on it although i dont really know what any of it means
***tampered***
***unlocked***
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
jun 11 2012,14:36:28
fastboot usb
vol up
vol down
power
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
im in need of a thourough stepo by step instruction on how to fix this thing i dont care if its by means of a custom rom stock rom whatevers easiest. i know how to utilize fastboot with instruction and ive changed back and forth between cwm and twrp but no matter how many tuts i follow i always end up in a loop and im not sure why again i apologize for being such a noob but ive come to realize that this forum is the best at fixing stupid problems like mine fairly quickly
thanks in advance for your help....
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Edit: Also, I'm assuming you have no knowledge of adb and fastboot commands? Because you might need to learn. And did you try this ruu? It's for your firmware version. http://forum.xda-developers.com/showthread.php?t=1814217
RollTribe said:
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Click to expand...
Click to collapse
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
frankthebunny said:
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
Click to expand...
Click to collapse
frankthebunny said:
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
Click to expand...
Click to collapse
Alright, so I'm assuming the problem is there is no ROM on the phone or someone did factory reset in bootloader. So if the ruu helps, great (it should). If not, then I'm sure we'll figure it out.
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
frankthebunny said:
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
Click to expand...
Click to collapse
Yup. Since you're on an older hboot there's no preparation needed. I'm assuming you don't really want to get into all this rooting stuff and just want a working phone? If you want help with rooting, come back here when the ruu is done, but if you like it stock, then you should be good to go :beer:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
actually i would like to root it after i get it all fixed and put a custom rom on it and what not. like i said earlier i can follow instructions this was just a difficult spot to start from ya know.
twistedddx said:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
right on ill do that. is there anything else i should be downloding now to prepare for what ever it is i need to do to protect my phone from messing up again?
exad said:
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
Click to expand...
Click to collapse
yeah it is an at&t phone. at least it says on the top of it however im using straight talk t-mobile i believe.
will i need to root it again in order to utilize the t-mobile carrier?
No need to root for your carrier.
But you will need to root again to install other roms.
So is this phone back up and running again yet?
Sent from my HTC One XL using xda app-developers app
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
frankthebunny said:
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
Click to expand...
Click to collapse
What ruu?
Did you relock the bootloader?
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
heres the name of the file
htc_one_x_RUU_2.20.502.7_att_us_08022012
frankthebunny said:
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
Click to expand...
Click to collapse
First do :
fastboot oem readcid and tell me what it says
if it's CWS__001 then do:
fastboot oem lock
And chill, your phone will work when I'm done with you.
it say
cid: 11111111
frankthebunny said:
it say
cid: 11111111
Click to expand...
Click to collapse
ok hopefully since it didn't say CWS__001 you didn't use the lock command.
do:
fastboot oem writecid CWS__001 (be sure to note there are two "_")
then do
fastboot oem readcid
It should now say CWS__001
please confirm
nice ok ive changed it now to CWS__001
hi guys, im not new to this, and i have a good understanding of adb and fastboot. i have just purchased a htc one xl (telstra) im running Hboot 2.15 and have unlocked bootloader via htc dev, installed TWRP ver; 2.6.0.0, rooted via flashing superSU and am currently running stock android ver 4.2.2 htc sense 5.0. i sim unlocked it so i could run my vodafone sim, and radio is working fine but i think the telstra RUU isnt allowing the sims internet conectis-on, therefore i am deciding to flash another rom. i first tried flashing pacman rom unsuccessfully but have yet to flash the boot.img as i havent got S-OFF and figure it wont allow writing to that partition yet, i have had alot of problems rewriting the CID for superCID, have tried many methods including xfactor and manually via fastboot and have been unsucessfull thus far, i understand that its not possible to downgrade Hboot unless S-off is achieved, alas facepalm is not possible unless superCID is achieved, and i cannot rewrite the CID manually or using any scripts i have found, is my Hboot version the problem or is there something im missing here?
help would be much appreciated
Have you tried the hex edit method?
Sent from my Evita
Yeah it returns with an error in adb, system mounted read only, and its deffinatly rooted so I'm not sure how to make system readwrite
Sent from my Wildfire S A510e using xda app-developers app
It would seem there s no sure fire way around this. Unless someone can help me figure out the read only issue in adb using the hex edit method
Sent from my Wildfire S A510e using xda app-developers app
hex edit progress
ok so i fixed the problem by uninstalling htcsync and re installing adb and fastboot via sdk tools, i got the file pulled from my phone and hex edited it, from cid; TELST001 to cid; 11111111 and pushed the file back onto my phone as per instructions, yet when i reboot into bootloader and do fastboot oem readcid it still comes back TELST001. somehow the phone knows what is happening and is changing the hex back to original form..??
ok scratch that, it actually never pulled the file from my phone, that was a file leftover from some script that didnt work, it had a cid of telus001 and my cid reads telst001 so i know that wasnt my file, the adb shell is able to read my phone but not ble to take the mmcblk0p4 file, so when i enter the command dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4 i get 2.0 records in 2.0 records out 1024 bytes transferred at <40960> bytes. so im guessing it was successful, yet when i check my sd root the file is nowhere to be seen!? where am i going wrong here
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
argh
O..K so i rebooted the one xl ad the file was there, i copied to desktop, hex edited, and did dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 to push the file back. read as successful in adb, so i did reboot fastboot and fastboot oem readcid, CID READS TELST001 STILL i must be retarded or something
timmaaa said:
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
Click to expand...
Click to collapse
ok thanks man, ill give it a go now
st3wy said:
ok thanks man, ill give it a go now
Click to expand...
Click to collapse
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
st3wy said:
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
Click to expand...
Click to collapse
i even tried doing echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
and still get INFOcid: TELST001
is it possible that my cid is stored somewhere other than mmcblk0p4 or mmcblk0p5??
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
timmaaa said:
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
Click to expand...
Click to collapse
sounds about right, i did read about this. so im guessing because i used temp root to spoof cid and unlock bootloader using the unlock code from that process, that there is no way to 'officially' relock the bootloader, and start the whole process again using a different method, say for instance using adb.. and thus getting bootlocker unlocked without spoofed cid and temp root possibly resulting in the ability to obtain supercid and full root? i have got supersu flashed through recovery.. but yeah obviously having serious issues with supercid atm.. thanks so much for your help this far man came a long way this arvo, just cant see the light at the ed of the tunnel... its like if i was able to flash Hboot i may be able to get around, but that requires s-off, which reuires super cid, which requires different Hboot lol
you wouldnt happen to know anyone else that might be able to brainstorm on this would you? although from looking at the threads youve made, it seems your possibly THE most educated person on this matter... idk might just have to wait for a dev to look into this and find a loophole. im not that good unfortunately. again, thanks for your help man. if you do get any ideas dont hesitate to post em up on this thread. cheers.
I'm definitely not the most educated person in this kinda stuff, I just read a lot on here and remember the ins and outs of this device. Finding a loophole around this is something that the HTC experts would have to work on, people like beaups, jcase, those kinda guys. Like I said though I'm not even sure if what I said is what's stopping you, I could be completely wrong.
Sent from my Evita
well, ive had one thaught that might be a stupid one but possibly one of the only things i am yet to try.. if i go through with the s-off and see if it works, although my phone is reading cid it may actually have supercid because like i say, its been successful in adb just hasnt returned a supercid through the fastboot commands, i guess the only question is will i brick my device if i follow through with s-off when i dont have supercid or will it just fail and all will be gravy
is there anyway to get them in on this thread so they know where im up to, or would i have to PM them exclusively and explain all over again
btw i think your right, system is read only. thats why the pushes arent working, even though they say they are in adb, either that or the phones cid and the RUU's cid are different and fastboot oem readcid is reading softwares cid and not the phones cid?
either way im going to drink a beer and go outside for a while, thanks again timmaaa, i didnt expect anyone to reply to this thread for a good while. like i said if u happen to have contact with the devs or anyone else that might be able to help, id be stoked. cheers bro and peace out!
You can try SuperCID but it just won't work. You can try contacting them and pointing them to this thread, but I think they're pretty busy guys so I don't know if they'll be able to help. The CID that shows up when using the fastboot command is definitely the phone CID and not the software CID.
Sent from my Evita
Yup, I know total newb question. I decided to unroot my phone a while back because honestly I knew I wasn't going to have time to mess around with the phone like I have in the past. I unrooted it and thought I did everthing right. Root checker says it's not rooted. However my phone has since messed up and broken and HTC is going to help me out under warranty and send me a refurbished one.
The phone is urooted but says it's unlocked and Supersu will not uninstall. When I turn it on using Power and volume down it says it's MODIFIED. I've since deleted everthing that helped me root the phone through the mack, all the files, etc.
Any help on how to get this back to normal? I've heard in a few places that they don't particularly care but I didn't want them to charge me once they receive the item.
Thanks for the help.
Ciresamor said:
Yup, I know total newb question. I decided to unroot my phone a while back because honestly I knew I wasn't going to have time to mess around with the phone like I have in the past. I unrooted it and thought I did everthing right. Root checker says it's not rooted. However my phone has since messed up and broken and HTC is going to help me out under warranty and send me a refurbished one.
The phone is urooted but says it's unlocked and Supersu will not uninstall. When I turn it on using Power and volume down it says it's MODIFIED. I've since deleted everthing that helped me root the phone through the mack, all the files, etc.
Any help on how to get this back to normal? I've heard in a few places that they don't particularly care but I didn't want them to charge me once they receive the item.
Thanks for the help.
Click to expand...
Click to collapse
Are you s-on?
I am, I remember I used this video but it did not lock and the supersu never uninstalled.
I'm trying to use these steps but it doesn't work, even though it finds my device:
http://www.andromods.com/unroot-locking/reset-unlocked-to-locked-htc-one-m8-bootloader-status.html
Ciresamor said:
I am, I remember I used this video but it did not lock and the supersu never uninstalled.
I'm trying to use these steps but it doesn't work, even though it finds my device:
http://www.andromods.com/unroot-locking/reset-unlocked-to-locked-htc-one-m8-bootloader-status.html
Click to expand...
Click to collapse
The best you can do then for now is to fastboot oem lock
And then run an s-on ruu that is the same or higher than what you have.
Will I be able to take off the supersu app at some point during this process? It will not uninstall
Ciresamor said:
Will I be able to take off the supersu app at some point during this process? It will not uninstall
Click to expand...
Click to collapse
The s-on ruu will wipe that puppy out lol
Okay thanks, I'm looking for an s-on ruu for the mac right now...
Ciresamor said:
Okay thanks, I'm looking for an s-on ruu for the mac right now...
Click to expand...
Click to collapse
Just do the zip method. I have them all posted in one thread.
Here:
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Nice, thanks! I'm running the fast boot oem right now, I'll let you know how it goes.
Hmm, I put the zip file and it says it can't open it...
Success, I wish it didn't say relocked but it no longer says modified, it states official on the banner.
Ciresamor said:
Success, I wish it didn't say relocked but it no longer says modified, it states official on the banner.
Click to expand...
Click to collapse
If the ruu wasn't lollipop and you paid for sunshine in the past you could do sunshine again and fix it
It was on lollipop and I didn't have the sunshine app.
is there any other way to fix that? What's the general consensus, will HTC void the warranty?
Ciresamor said:
is there any other way to fix that? What's the general consensus, will HTC void the warranty?
Click to expand...
Click to collapse
Locked is locked. Whether relocked or locked. You cannot fix that without being s-off. If you are still on kitkat you could pay $25 via sunshine to s-off and fix it to say locked and then turn s back on.
Well I'm going to send the phone out and see what happens. Thanks for your help in this thread.