I've searched a lot of threads on this site in hope of finding a solution to my issues, and none of them work. I'm using an HTC One X and well, I'm trying to modify it. I use the steps prescribed on HTC Dev however, once I get to step 12, it says ,token check failed, every time. Every time I input fastboot oem get_identifier_token, I get a different code, and I test it to see if it will work. However, nothing does. I've also tried to update my device to 5.18 in hopes of the bootloader already being unlocked as it it apparently does in later models. All I get it is Error 158: Image Error which, everywhere I look, I find no explanation. I have no idea at all why so many things are going wrong. My phone has never been rooted or tampered with, or modified, it has always worked fine. Maybe it's a CID issue. Either way, I have no idea. Can someone help me? I just want to get this dang bootloader unlocked. This should not be this much of a head ache.
Related
I tried to unroot my desire, its being collected tomorrow for warranty repairs. I seem to be stuck with the 4 exclamation marks and the htc logo
when I try and flash the vodafone RUU which I thought my phone was, I get CustomerID error.
I tried a couple of other Europe and WWE roms and I get 140 bootloader error - I dont think Ill be able to make a gold card from here (can I)
any suggestions late night people?
L1ndon said:
I tried to unroot my desire, its being collected tomorrow for warranty repairs. I seem to be stuck with the 4 exclamation marks and the htc logo
when I try and flash the vodafone RUU which I thought my phone was, I get CustomerID error.
I tried a couple of other Europe and WWE roms and I get 140 bootloader error - I dont think Ill be able to make a gold card from here (can I)
any suggestions late night people?
Click to expand...
Click to collapse
bortak's useful troubleshooting guide
Thanks for the link - its a great guide, I could have done with it in the wee hours last night.
So I fixed it this morning, with only 40 mins to spare until collection time for warranty repair.
Here's what happened in case its of use to anyone else, same kind of problems
I didnt know you had to downgrade your alpharev s-off before returning to stock , I was running cm7 r2 version. (I still cant find the definitive answer on this, but I think you do - I only vaguley know what it does, enough to get in trouble)...
When I tried to run the RUU uk vodafone, without downgrading s-off, I got an error saying the RUU file was corrupt or it couldnt write the file. (Maybe because the Ram was distributed differently not enough space)...anyway it didnt work and I got stuck at the screen with four exclamation marks (4 !) in the corner, though when I unplugged it went to the white bootloader screen, which said bootloader version 0.00.000
I read somewhere to change s-off and managed to do that via fastboot commander, but then when I tried the RUU it stopped because Customer ID was wrong.
I tried several different RUU's just in case, but most of them gave an Incorrect bootloader error, and the vodafone ones gave the CID error.
I couldnt make a goldcard easily because I no longer had a phone, but by morning I found someone with an android phone... and managed to make a goldcard (which certainly wasnt without its difficulties, but was worth it). Just in case you find yourself in the same position, to make a goldcard the easy way, you need a phone, BUT ANY ANDROID will do, it dosent have to be your own, the numbers needed are from the sd card not the phone.
I then tried the early vodafone RUU again, same bootloader error, presumably something to do with how early a version it was, then tried a later version, and it worked.
I've never been so happy to see an electronic device booting up... 40 mins before the collection man was due (he still hasnt come though lol - 4 hours later)
I wrote this just to close the thread, and in case anyone had similar difficulties.
Hello fellow One-X'ers, I am coming from a long line of Samsung devices and have only had one HTC phone in the past, (HD2).
I cant for life of me figure out how to root this phone, I have tried the conventional method, alternate root method, im getting nothing... Bootloader will not unlock through htcdev (which it says to do in half of the root how-tos), i always see error 160 invalid MID...
I have installed and updated the following:
-Java
-HTC Mobile drivers as well as sync
-SDK
-Fastboot
wtf am I missing here? I just want to get a new rom as this sense stuff absolutely sucks. Yes I have searched, yes I have read...
What phone have you got? If I remember correctly the "Error 160" / "invalid MID" responses are returned when you try and use HTCDev to unlock the AT&T One X (actually the One XL) which doesn't support unlocking the bootloader in that way.
Boot into the bootloader and check the model name displayed at the top of the screen: if it says "evita" then that's your problem, and you'll need to head over to the forums for your particular device to get some help because none of the stuff in this section will work - http://forum.xda-developers.com/forumdisplay.php?f=1538
If the bootloader shows "endeavoru" then you are in the right place, but in that case I don't know what the problem is.
Uninstall HTC sync, keep the USB drivers mind.
Sent from my HTC One X using Tapatalk 2
Seriously, I'm so pissed off with HTC right now that I just wanna throw this piece of crap into the wall. This is the last time I'm buying a HTC phone unless they unlock bootloaders from the start.
So I relocked my phone few days ago because I wanted to install JellyBean, but it turned out that EVERY damned mobile operator except mine have released JellyBean. So now I wanted to unlock it, downloaded the tools (http://forum.xda-developers.com/showthread.php?t=1604439). Got my Token ID, downloaded the unlock file, but when I try to unlock it I get some weird error (sending "unlocktoken" <0 KB>... FAILED <unknown status code>)
And that's where I'm stuck.
So I thought I need to download and install OpenSense SDK. Downloaded it, but of course, when I start it nothing happens, it just closes itself.
And then there are a bunch of idiotic errors on HTC website like "You have exceeded the allowed page load frequency." when I try to scroll from one page to another. My god.
The token id that you are sending to the device
Seems to be corrupt. It can not be of 0kb size. Try tree downloading it.
Sent from my unlocked HTC One X using XDA premium.
:angel: patience man. are you the one who unlock your phone before? if yes. you can use the unlock code.bin you used when you first unlocked your phone.
Does samsung unlock their bootloaders from the start?
No one unlocks their bootloaders from the start, not even Nexus devices, but they have very easy bootloader unlock methods. HTC gave a half-assed, convoluted method and Motorola is even worse than HTC. The bootloader unlock process of HTC is fine, nobody expects them to ship phones with unlocked bootloaders, but the unlock should result in S-OFF. There's no reason it should remain S-ON.
Sent from my Desire HD using xda premium
Yes, I was the one who unlocked the phone from the start. I never had any issues, it's just after I relocked it that it suddenly is refusing to unlock again.
The unlock code is actually 1kb, not 0. Dunno why it says 0 in the error.
Just make sure you run the unlock command in fastboot mode not hboot mode.
I was in fastboot usb mode when I tried to do everything.
Alright, now that I cooled down. I'm gonna see what I can do again.
I got it working, managed to unlock the exact same way I tried before, with the exact same file, just with the updated tools that were released yesterday.
Sometimes fastboot can be a pain in the A$$.
Might have been the same problem you faced
If i enter an incorrect command in fastboot (i.e. I spelt something wrong) it will not accept any more commands for the rest of that session until i reboot.
When flashing the unlock token mine also gives me an error but it still works
If I try an invalid fastboot command then try to flash the token. I get the same error but it doesn't work.
Figure that
Personally i think its just poor software on the one X, i point the finger at the device because i had no such problems with these types of commands on the Nexus 7 & Nexus One
there are commands that when tried will actually crash the phone rather than giving an error, such as fastboot oem writesecureflag 0 (code for turning S-OFF)
you would expect an error saying not allowed or something but instead the phone just locks up forcing you to hard reboot
Sent from my HTC One X using xda app-developers app
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
You need to ask in the m7 sections. This is the m8 area. What rom was it running? . I have a couple things to try if it's a Verizon one.
m7misery said:
Well after almost a week of Googling, I've given up.
My Dad's HTC One M7 seems to be soft bricked (i.e. No OS), and will only enter the fastboot menu. All options therein (factory reset, fastboot), just put the device back in fastboot mode.
I then tried to unlock the device on the HTC site. I got to the final stage (flashing with unlock code, which shows as successful on my computer), and the confirmation screen on my phone does not appear. It is still showing *LOCKED*.
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF. My S is most definitely ON. To make it S-OFF, I think I'd need to boot onto an OS and enter debug mode.
I have an OTA file for my carrier which seems to be up to date. Is there any chance this would help?
So I'm sort of chasing my tail here, any help would be appreciated. One possible solution would be if I could possibly unlock a bricked device? (A rare request from what I gather, as most phones are bricked after custom ROMs).
I find it so frustrating that this has happened when I've never even rooted/unlocked the device. I'd never seen the bootloader menu before this.
Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
maybe best to see if you can unlock it via HTC Dev(as u are in fastboot mode)
Then install custom recovery, full wipe and flash a new rom via adb sideload, that will give you the system back and it should boot.
m7misery said:
Moving from here the only option seemed to be an RUU, however this only seems to work with S-OFF.
.
Click to expand...
Click to collapse
This is false. RUU is designed to run on stock devices and will run just fine with S-on or S-off as long as you are running the correct RUU for your version (and also the RUU number needs to be equal or greater than what is on the phone, you can't "downgrade" while S-on).
But as mentioned previously, this forum section is for the M8 as clearly noted in the forum title. You need to get advice in the M7 forum, as advice given here (applicable to the M8) can be incorrect or even harmful to your device.
I wonder if anyone can help me with my unlocking issues?
I have an HTC Desire A8181 that is locked to T-Mobile and I now need to use it with 3UK. Every time I insert my 3UK sim, I get a prompt to enter an unlock code, but don’t know what to enter here.
I have tried using an unlock tool which is mentioned elsewhere on the forum, but it unfortunately fails to work for me.
I tried using ‘HTC DESIRE SIM-UNLOCK UTILITY v0.9.5’ but every time, it returns Error 13a: AdbReadEndpointSync returned error 31. Waiting for hboot!……………….
How do I get to unlock my Desire A8181 Bravo? Is there a keygen or something that can provide a code, or am I out of luck? I hope someone out here who is more knowledgeable could help out with this one.
Thanks for reading. Regards, Tony (Brookbond) See photos.
Try downgrading the HBOOT version to one that Revolutionary supports so you can do an S-OFF and change the CID to SuperCID (11111111).
Since everything has been described in various threads and posts, I won't duplicate it.
ze7zez said:
Try downgrading the HBOOT version to one that Revolutionary supports so you can do an S-OFF and change the CID to SuperCID (11111111).
Since everything has been described in various threads and posts, I won't duplicate it.
Click to expand...
Click to collapse
ze7zez, thanks for the reply, I think I may be out of my depth a little with this phone. I did have HBOOT v0.93.0001 on the phone and I did try several times to use HTC Desire Sim-Unlock Utility v0.9.5 by sieempi, without success.
It found the phone, confirmed the serial number of the phone, rebooted the phone into hboot, then displayed ‘Error 13a: AdbReadEndpointSync returned error 31, Waiting for hboot……………………………
I have little knowledge on the subject really, and I know that little knowledge can be dangerous. I don’t really know where to go with this now, as I had already tried the above sim-unlock utility several times when the phone had HBOOT v0.93.0001 and that failed to work for me.
I was hoping for a keygen to produce an unlock code, but not sure if such a fix exists? Is there anywhere I could find a code to enter into the phone to unlock it?
I am prepared to backtrack and downgrade the hboot version as a last resort. Any suggestions please?
Thanks, brookbond (Tony)