Anyone know why it won't generate a token for me? I feel like I'm making a stupid mistake here, but it reboots to fastboot, tells me to copy the ID token and paste it into the HTC page. Makes sense, but there's no token to copy?
tekhna said:
Anyone know why it won't generate a token for me? I feel like I'm making a stupid mistake here, but it reboots to fastboot, tells me to copy the ID token and paste it into the HTC page. Makes sense, but there's no token to copy?
Click to expand...
Click to collapse
Are you requesting the token from the command prompt while connected but not active sync. I think the command is fastboot get_identifier_token or whatever is on the HTC dev site. Then the in the command prompt it will suddenly display like 17 lines of code ..it will have a start and a stop..
mjh68 said:
Are you requesting the token from the command prompt while connected but not active sync. I think the command is fastboot get_identifier_token or whatever is on the HTC dev site. Then the in the command prompt it will suddenly display like 17 lines of code ..it will have a start and a stop..
Click to expand...
Click to collapse
Yeah, I just did it in the command line. HTC Super Tool is supposed to just run the script for you, but it didn't seem to work for me. The get identifier command worked just fine.
i had the same problem so i ran it manually
Okay, so i have looked and searched all the forums and yet no answer..
First thing first: I have a Mac - so i found the thread for using the terminal and getting the unlock code from HTCdev - no prob it was easy
Now here is where I get stuck i save the Unlock_code.bin into my android folder but when I go into terminal I get this message and I have tried with diff. generated tokens and codes.
/android/fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
Suggestions ??
Help!! and since I am a NOOB i can't post in the XDA developer forum where most likely there is an answer - no offense.
This might be a long shot, but when you copy and paste the code, is there something like INFO or bootloader in front of every line? I remember seeing somebody having that problem, and they were also on a mac. If there is, do the code without that and it should work.
I already did that received the email from HTCdev and the attachment saved it in my android folder and when I go to do the last step i get that error message.
You can't post in the dev forum because that is for releases only so you wouldn't be helped if you posted there. Have you tried flashing the token with windows? Does fastboot have the correct permissions to read and write to the folder?
huh
this is my 1st android phone... i have a macbook pro. So what do you mean flashing the token with windows?...permissions as far as? I'm on the verge of jus sayng f it.. not worth this much worth was easier to unlock my blackberry and my ipod than this smh...
i did exactly every steps that show. but how come when i submit.
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: 140.
Error Reason: Token Decryption Fail.
Help!!!!!!!!!!!!!!!!
try going thru the whole process again, gettin the token and make sure u copy the "<<<<<<<<" too
Make sure you copy your token identifier in a notepad and delete "info" on the left side.
This should be posted in Q&A section.
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this how i copy.
dt53444 said:
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this how i copy.
Click to expand...
Click to collapse
That looks correct. So you already got your Unlock_code.bin?
<<<< Identifier Token Start >>>>
82520115AFCD5337DCDC6485A6D7D4B8
376D2DF9939BF47E6378597AFD70F7DF
451558E2810941B9D81C93F5DDC9EF95
3479EA6AD52893243D92159DB9CE811B
04C0CDF6110E7A639ABA2594AF8B554C
2EA1C220CBF75B9920AB072A839819C7
1F439E0D2A48068759FD2F2FB378C758
758CBE0CAE55F316C6BE8B0084209B5B
54C150522AD3F3265C053B6911BA6F14
23C2B5B88BC74AB3792A0704B6563F11
62D6B0BACB741AE287F9FDAD7C022CF5
B691FAEB0C4C2E79B82012695A1B5298
C29F5B396397047A77007643C9ADE588
61F90A391B7AC0945E264CA500C978AB
F03F42FE9A3E7584508FEA909CD2D82F
135C461490BE1978ED2A8DD814C37535
<<<<< Identifier Token End >>>>>
this is how i copy
still got same error!!!
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
i got it people. Thank you
What was the problem?
I'm facing the same issue
Make sure you aren't selecting the empty column just to the left of the token identifier. There is a single vertical line to the left that sometimes gets selected if your not carefull. I am willing to bet that this is your problem.
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
shellguy said:
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
Click to expand...
Click to collapse
i rooted before htc dev so that shouldn't b your problem also read this thread cause alot of ppl are having a difficult time selecting the token
I get
C:\Users\mark\Downloads\android-sdk_r12-windows\android-sdk-windows\platform-too
ls>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
and it just sits there. Only way to end it is to unplug phone. RUU'ed and updated htc sync then went through the whole process again and still nothing.
ummm am i an idiot..but i dont see the evo 4g lte listed on htcdev...which one are ya'll selecting
dahray02 said:
ummm am i an idiot..but i dont see the evo 4g lte listed on htcdev...which one are ya'll selecting
Click to expand...
Click to collapse
At the bottom "All Other Supported Models"
shellguy said:
Mine is getting to this point:
c:\Android>fastboot oem get_identifier_token
< waiting for device >
and then just sits there. Is this because I rooted before doing HTCDev?
Will
Click to expand...
Click to collapse
Make sure you have the proper drivers installed if not adb wont communicate with the phone.
Sent from my EVO using xda premium
durandetto said:
Make sure you have the proper drivers installed if not adb wont communicate with the phone.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I used the same PC to root the device too, but that was done via script.
Will
I'm having a problem as well. I got my Unlock code email. I downloaded it and put it in the Android file I created. Highlighted folder, shift+right click, got my cmd prompt, copied and pasted the fastboot flash unlock token...... and got this:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
C:\Android>
I don't remember having any issues when I did my Evo3d????????
FIXED: Had to actually type command. DO NOT copy and paste
shellguy said:
I used the same PC to root the device too, but that was done via script.
Will
Click to expand...
Click to collapse
Do you have adb installed?
Did you put in the path in your environment variables?
Do you have have HTC sync or disk drive disabled?
Is USB debugging on?
Lastly, computer OS? sometimes its just easier to use xp than w7.
If the answer to the first 4 questions were all yes, it should work...
What? XP is kicking my a$$! When I'm on a friends win7 PC, it finds drivers right away. Hell, I still can't even get XP to recognize my device storage to put my music on my phone (adb sees my device just fine and fastboot commands dont work either). Driving me nuts.
sent from my Evo LTE, usually.
i can get to step 3 in getting my token i.d. once i get to step 4 which is submitting the token i.d in the htcdev site i get an error saying invalid i.d. am i doing something wrong or is my device not supported? i have an at&t htc one m8. please any help or any ideas on what went wrong??
edit:nvm pls delete thread got it unlocked,rooted and twrp recovery
I succeeded in doing the following:
1) downgrade my tablet to a rootable fw version
2) rooted with doomlord tool
Now I need to unlock my bootloader: I had requested the key a while ago, but never got around to using it.
I followed all the instructions and succeeded in connecting the tablet in fastboot mode to my pc (drivers installed fine and I receive a reply when issuing the trial command getvar version, meaning, I presume that the device is connected and able to receive commands and reply to them).
However when I issue the command in the instructions on http://unlockbootloader.sonymobile.com/instructions and replace the final "KEY" with the key provided by Sony via email I receive a reply "FAILED (remote: Command did not succeed)": what could I be doing wrong? I also copied and pasted the command in order to make sure that the syntax was correct and checked the code I input many times to make sure I did not miss or messed up something, but it all seems OK. I issued the command from within the same directory where the getvar command was issued, i.e. within Android SDk/Tools folder (the procedure on the website doesn't suggest to change folder, so I didn't!) , but no success at all!
Can anyone suggest some way out?
Thanks
Luca
astrovale said:
I succeeded in doing the following:
1) downgrade my tablet to a rootable fw version
2) rooted with doomlord tool
Now I need to unlock my bootloader: I had requested the key a while ago, but never got around to using it.
I followed all the instructions and succeeded in connecting the tablet in fastboot mode to my pc (drivers installed fine and I receive a reply when issuing the trial command getvar version, meaning, I presume that the device is connected and able to receive commands and reply to them).
However when I issue the command in the instructions on http://unlockbootloader.sonymobile.com/instructions and replace the final "KEY" with the key provided by Sony via email I receive a reply "FAILED (remote: Command did not succeed)": what could I be doing wrong? I also copied and pasted the command in order to make sure that the syntax was correct and checked the code I input many times to make sure I did not miss or messed up something, but it all seems OK. I issued the command from within the same directory where the getvar command was issued, i.e. within Android SDk/Tools folder (the procedure on the website doesn't suggest to change folder, so I didn't!) , but no success at all!
Can anyone suggest some way out?
Thanks
Luca
Click to expand...
Click to collapse
Sorry if this is a dumb question, but is bootloader unlocking allowed on your tablet ?
Some service providers have blocked bootloader unlocking.
GretaLewd said:
Sorry if this is a dumb question, but is bootloader unlocking allowed on your tablet ?
Some service providers have blocked bootloader unlocking.
Click to expand...
Click to collapse
I followed the procedure on the Sony website to check that and the answer is yes, it can be unlocked.
I tried some other tutorials and no results. It seems that it might be connected to the doomlord exploit (which I used to gain root access), but all the instructions on how to get around that have failed to allow me the unlocking!!!!
astrovale said:
I followed the procedure on the Sony website to check that and the answer is yes, it can be unlocked.
I tried some other tutorials and no results. It seems that it might be connected to the doomlord exploit (which I used to gain root access), but all the instructions on how to get around that have failed to allow me the unlocking!!!![/QUOTE
SOLVED
Click to expand...
Click to collapse