Hello, i have this problem when i trying to take the Unlock_code.bin from htcdevs
-Error Code: Invalid Bootloader Token Length.
-Error Reason: The submitted Token appears to be the wrong length and won\'t work.
I did all 20 times correct, space etc......any solution?
---------------------------------------------------------------------------------------------------------------------------------
Its ok....my PC fault, i did it from my mobile.
similar issue
liontarion said:
Hello, i have this problem when i trying to take the Unlock_code.bin from htcdevs
-Error Code: Invalid Bootloader Token Length.
-Error Reason: The submitted Token appears to be the wrong length and won\'t work.
I did all 20 times correct, space etc......any solution?
---------------------------------------------------------------------------------------------------------------------------------
Its ok....my PC fault, i did it from my mobile.
Click to expand...
Click to collapse
I can't even get to that step....I'm stuck on trying to get my computer to recognize my phone. I'm stuck on the cmd. Tells me "waiting for device" when I'm in fastboot usb mode on my phone. I unstalled htc sync but kept the drivers and made sure they were up to date in device manager. Im on win7 64bit. Any suggestions?
Maybe you have an app in pc that needs usb debugging like moborobo or something.
Sent from my HTC One SV using Tapatalk
solution...
liontarion said:
Hello, i have this problem when i trying to take the Unlock_code.bin from htcdevs
-Error Code: Invalid Bootloader Token Length.
-Error Reason: The submitted Token appears to be the wrong length and won\'t work.
I did all 20 times correct, space etc......any solution?
---------------------------------------------------------------------------------------------------------------------------------
Its ok....my PC fault, i did it from my mobile.
Click to expand...
Click to collapse
For future use.
I erased the HTC cookies from my browser and proceeded to process
Related
Ellos All. So I'm attempting to unlock the bootloader on on my Sensation. I'm following the instructions given via htcdev.com, everything was going okay but now I'm in CMD Prompt at the stage where I use the command fastboot oem get_identifier_token, and instead of the line of text that I'm supposed to get, I get <waiting for device> ... Any suggestions? thanks!
Did you follow the instructions? I've also done the HTC unlock method and it's flawless. I revolutionary'd after that but that's besides the point.
Not trying to sound like a douche, but you definately missed something. Maybe you didn't enable USB Debugging.
just do the s-off/rooted thing by this forum :
http://forum.xda-developers.com/showthread.php?t=1192300
and you will succed in 1 time oh and dont forget htc sync need to be on at phone with usb debugging
Yes, I've followed the instructions
I had a similar problem. I simply rebooted the phone (while it said "waiting for device") and all went well after that.
kaustic187 said:
Ellos All. So I'm attempting to unlock the bootloader on on my Sensation. I'm following the instructions given via htcdev.com, everything was going okay but now I'm in CMD Prompt at the stage where I use the command fastboot oem get_identifier_token, and instead of the line of text that I'm supposed to get, I get <waiting for device> ... Any suggestions? thanks!
Click to expand...
Click to collapse
first Enable USB debugging on phone . Boot your phone into bootloader. Connect your phone to pc via usb cable. Phone should read FASTBOOT VIA USB.
Make sure that HTC sync is off . ( Go to task manager, if you see the HTC sync is running, kill it)
Also remove anything else that may attempt to sync when you connect device.
Eg doubletwist, isyncr etc.
i did all necessary stuff according to this tutorial: (windows 7, 64 bit)
http://forum.xda-developers.com/showthread.php?t=1583427
just after typing: fastboot oem get_identifier_token
cmd says: <waiting for device>
and now it just freezes at this point, i don't get any further
anybody got some advice?
garldehildehar said:
i did all necessary stuff according to this tutorial: (windows 7, 64 bit)
http://forum.xda-developers.com/showthread.php?t=1583427
just after typing: fastboot oem get_identifier_token
cmd says: <waiting for device>
and now it just freezes at this point, i don't get any further
anybody got some advice?
Click to expand...
Click to collapse
Sure. This happened to me at first. Try connecting your phone to a different USB port? Did you get a taskbar notification that a device had been connected? (Did you here the little dings? ha)
When cmd says waiting for device, it either means that your phone isn't in fastboot (which I assume it is, since you were following the directions), or that the device isn't connected.
Also, did you install the software package HTC sync? It's a fairly large download, but it might be a necessary one to get the required drivers to connect the phone.
Let me know if this helps.
Make sure you've installed the usb drivers required by selecting the check box for USB in the Extras.
Yep I got this error too and just had to install HTC sync from the HTC website to fix it. Easy peasy
Just use this guy's toolkit. Worked on my U.S one S.
http://forum.xda-developers.com/showthread.php?t=1604677
Sent from my HTC VLE_U using xda premium
well i downloaded this htc-sync stuff you said and everything just works fine
thanks a lot guys!!
Hello,
So I'm trying to unlock and root my tf700t now that my warranty is expired and hope for an ASUS update is diminishing. I downloaded the unlock app from the website and went through the procedure. It took a few weeks and several emails with ASUS support but I think it is unlocked. The reason I say I think its unlocked is whenever I reboot the device, I don't get the message that says its unlocked. The unlock app however says the device is unlocked. So is my device unlocked?
I operated under the assumption that it was and tried to install the twrp recovery using the minimal adb and fastboot exe file. My tablet is recognized by my PC and I put the tablet in fastboot. The error I get when I do that is a writing error. It says writing recovery.... FAILED <remote: <INVALID STATE>>. Does this mean that I am not unlocked or did I do something incorrectly? Any help would be appreciated. I've been working on this for a few weeks and really want to get it moving.
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
berndblb said:
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
Click to expand...
Click to collapse
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Jkeeper18 said:
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Click to expand...
Click to collapse
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
sbdags said:
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
Click to expand...
Click to collapse
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Jkeeper18 said:
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Click to expand...
Click to collapse
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
berndblb said:
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
Click to expand...
Click to collapse
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
I am in the same boat - they think it is unlocked but it is not
The Asus v7 and v8 bootloaders both say "device is unlocked" but the fastbook info shows that it is not. I do not see any unlock inormation after the boot process starts. Also , the unlocker did not automatically restart my tablet. It also asked for my google credentials the first 5 times until the unlock said it worked. Now it does not ask that, it just says that it is unlocked. When I try to fastboot install the TWRP rom, it fails.
(remote - invalid state)
I called Asus and they have my tabler listed as unlocked. They are opening a case so that I can prove that it is unlocked.Then hopfully if they reset that setting, I can re-unlock it...
I was following this thread:
http://forum.xda-developers.com/showthread.php?t=2571542
Is there any work around? Please help!
I want TWRP and CM 10.2 on this slow TF700T tablet.
Thanks!
Jkeeper18 said:
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
Click to expand...
Click to collapse
Well you typed fastboot device not fastboot devices.
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
berndblb said:
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
No, I did not have two-step verification. I hope Asus creates a case and actually looks into it and resets my device's status in their system. It sounds like that is my only option -- a very lengthy and painful one.
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
Well you typed fastboot device not fastboot devices.
Click to expand...
Click to collapse
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Jkeeper18 said:
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Click to expand...
Click to collapse
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
berndblb said:
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
Click to expand...
Click to collapse
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Jkeeper18 said:
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Click to expand...
Click to collapse
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
sbdags said:
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
Click to expand...
Click to collapse
Sorry Im still new at this. Where is the fastboot folder?
Jkeeper18 said:
Sorry Im still new at this. Where is the fastboot folder?
Click to expand...
Click to collapse
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
sbdags said:
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
Click to expand...
Click to collapse
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Jkeeper18 said:
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Click to expand...
Click to collapse
I have followed the TF700 forums for the last year pretty extensively and until about 2 weeks ago never read about anyone having this problem: Asus database having you unlocked, but it actually isn't. Since then I think I've read about 4 cases.
My best guess: It's a problem with the v8 Unlock app or the way their servers store/process the information they get from the Unlock Tool.
That you got to a support person willing to contact Taiwan is a big plus already. Other users just ran into a wall of: We do not support unlocking this device.
So stick with the person you contacted already. Take pictures of your boot process (to document that it does NOT say: This device is unlocked) and they always seem to ask for a screen shot of your About Tablet page with your SN number and MAC address.
Persistence seems to be the key. And luck to get someone at Asus willing to help....
There is no other way to unlock the bootloader. So you would be limited to rooting the tablet which would give you more freedom to tweak it and uninstall bloatware, but you still would have to deal with the slow stock rom.... :fingerscrossed:
My phone stopped working all of a sudden, and when I restarted it entered the fast boot mode iteratively.
If I select recovery or normal boot, or whatever it says the same msg, "recovery image not valid".
The phone was unrooted, so I thought of rooting it.
I dont remember the status of usb debugging in my phone was on/off, now no chance to check it either.
But i could run the commands from the cmd to get the unlock data code, as well i received the code from Motorola to unlock.
When I tried the fastboot oem unlock (20 digit Unlock code)
I used to get a reply: Unlock data invalid!
Failed (failed remotely)
And some time info of time ~10s.
I also ran the getvar all command & noted the cid= 0x0007 (I dont remember count of 0's but ending was 7 which I found the device is unlockable)
I live in India & the device is not network restricted and I have bought it from flipkart.com which was sole retailer of Moto devices in India.
Can someone plz help....
Thanks,
Swapneel
XDA Visitor said:
My phone stopped working all of a sudden, and when I restarted it entered the fast boot mode iteratively.
If I select recovery or normal boot, or whatever it says the same msg, "recovery image not valid".
The phone was unrooted, so I thought of rooting it.
I dont remember the status of usb debugging in my phone was on/off, now no chance to check it either.
But i could run the commands from the cmd to get the unlock data code, as well i received the code from Motorola to unlock.
When I tried the fastboot oem unlock (20 digit Unlock code)
I used to get a reply: Unlock data invalid!
Failed (failed remotely)
And some time info of time ~10s.
I also ran the getvar all command & noted the cid= 0x0007 (I dont remember count of 0's but ending was 7 which I found the device is unlockable)
I live in India & the device is not network restricted and I have bought it from flipkart.com which was sole retailer of Moto devices in India.
Can someone plz help....
Thanks,
Swapneel
Click to expand...
Click to collapse
Hello,
You may register for a XDA account so that we could help you move this thread to right Q&A section in order to get expertise help.
-Vatsal
Just as the title says; I have the unlock token and I've tried everything I can think of to flash it and nothing's worked. I have OEM unlocking enabled, the phone is permanently carrier unlocked, USB debugging is enabled, I've made sure to download a new version of Platform Tools, I've moved the .bin file to the same directory as Platform Tools, the phone comes up in ADB and fastboot when I check, it just won't write and I can't figure out why... usually it just hangs at sending 'cust-unlock' etc. but never progresses past that. Can anyone help me figure this out?
EDIT: Resolved! Me being dumb, not realized I'd only tried USB 2.0 ports; using a 3.2 port did the trick instantly.
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
FoxyDrew said:
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
Click to expand...
Click to collapse
Yea, that's what's baffling; I can jump back and forth between adb and bootloader/fastboot pretty easily but I just can't send the unlock token. I have seen a couple weird errors though, like if I'm in bootloader and do 'fastboot OEM unlock' and it fails (since I can't get the token to flash) and afterward I try 'fastboot devices' sometimes fastboot crashes to the 'press any key to reboot' screen.
Could this just be an outdated driver issue? I thought they were up to date...
Have u try using other cable or even try on different PC?
hendavi said:
Have u try using other cable or even try on different PC?
Click to expand...
Click to collapse
I've tried multiple USB ports and the original cable as well as others; I've confirmed commands like 'ADB reboot bootloader' and 'fastboot reboot bootloader' work and I've even updated the ADB/fastboot drivers just in case... still nothing. I haven't tried a different PC yet but I suppose that's next
No matter what I try, this is what I get every time I try it from the bootloader. I've tried from bootloaderd/recovery, but it fails there too saying something like 'writing not allowed' or something... I have OEM unlock turned on and it's carrier unlocked, so I have no clue what's stopping this from working.
What's really weird is I actually got this to work once before on this same device, but had to reset the phone back to stock T-Mobile branded software using the MSM tool; the first time around, I was able to enter the unlock token and just unlock it like normal (fastboot OEM unlock). Now that I've reset the phone and I'm trying again, it just won't work... really perplexed on this one.
UPDATE
I had to pull up an image of my mobo's io panel because I couldn't remember and couldn't see which ports were which; once I moved the cable to a USB 3.2 port, it worked... I guess I'd only been trying it on USB 2.0s before so it didn't work.
Thanks for your help!
I had same issue on my OnePlus 8 TMobile. Have to disable driver signatures. This shows you how. Yes, the link is for a diff phone, but just follow the disable driver signatures part of it and it will then show up in fastboot
https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
EDIT: False alarm. I was sent an unlock code for an older device I have instead of the one I just bought. Should've double checked it first.