I've spent at least 6 hours today trying to figure this out. I've (tried) following numerous guides. I've never used ADB and I am have a lot of trouble with that. I've tried using the one-click tool, that doesnt work. This seems extremely complicated. More complicated than any other phone I've rooted and unlocked. Is it a Windows 8 issue?
I did it, it was a pain however I had other issues with win8 such as all large file downloads would freeze up then my dl speed would skyrocket then appear to be downloaded and were corrupt. Ive since reverted to win7 and my s3...DNA wasnt cutting it for me but ill return to DNA later on down the road, what issue you having? getting adb? I had to change my usb drivers
nolimitzr2 said:
I did it, it was a pain however I had other issues with win8 such as all large file downloads would freeze up then my dl speed would skyrocket then appear to be downloaded and were corrupt. Ive since reverted to win7 and my s3...DNA wasnt cutting it for me but ill return to DNA later on down the road, what issue you having? getting adb? I had to change my usb drivers
Click to expand...
Click to collapse
Yes I am having trouble getting ADB. How did you change the USB Drivers?
art0605 said:
Yes I am having trouble getting ADB. How did you change the USB Drivers?
Click to expand...
Click to collapse
for me, to get the drivers to work i had to install htc sync.
If you plug in your phone, you should have 2 virtual cd's, one of them HTC sync.
After you get it installed, open a command prompt using administrator privileges (even though i am admin on my pc, i had to do this anyways)
and try running the command ADB devices and see if your phone shows up. that's what i had to do to get it to work.
Cdoan34 said:
for me, to get the drivers to work i had to install htc sync.
If you plug in your phone, you should have 2 virtual cd's, one of them HTC sync.
After you get it installed, open a command prompt using administrator privileges (even though i am admin on my pc, i had to do this anyways)
and try running the command ADB devices and see if your phone shows up. that's what i had to do to get it to work.
Click to expand...
Click to collapse
I am pretty sure I did the exploit correctly. But when trying to submit the token, I get Error Code: 160.
Try right clicking on the root program if there is an AIO and select compatability and chose windows 7
Sent from my SCH-I535 using Tapatalk 2
Related
The driver install fails on the HTC MTP driver install...I cannot get by this. I am running Windows 7 64 bit...anyone else having this issue?
OMG I fought with that for HOURS. I never did get them to work. I installed htc sync, htc sync manager, and I installed the all in one kit drivers.. Nothing. Windows 7 64 bit too.
I assume you are trying to unlock the bootloader and root?
Do both things manually using fast boot commands and recovery.
Tl;dr you can root without MTP drivers
wdkingery said:
OMG I fought with that for HOURS. I never did get them to work. I installed htc sync, htc sync manager, and I installed the all in one kit drivers.. Nothing. Windows 7 64 bit too.
Click to expand...
Click to collapse
exactly like me, I have been fighting with this for two days now. Reinstalling htc sync, htc sync manager, cleaning out existing drivers reinstalling again. Removing everything that could be associated with htc at all, reinstalling android sdk etc etc.
Nothing makes my phone recogniced by ´adb devices´not even htc sync software recognice it.
Every time I plug it in, the device is recogniced and installed and it says under Portable Devices in the device manager ´HTC One X+´
Do you get the Choose type of connection screen on your phone when connecting it? Because I dont, is just says connected in debug mode, even if debug development tools is turned of and debug of. But it still doesnt show up in adb.
denne2 said:
Do you get the Choose type of connection screen on your phone when connecting it?
Click to expand...
Click to collapse
No, not on this phone.. I think it has to do with the MTP crap. You can read an informative post by Lloir in the dev section to find out more.
wdkingery said:
No, not on this phone.. I think it has to do with the MTP crap. You can read an informative post by Lloir in the dev section to find out more.
Click to expand...
Click to collapse
hmm.
went back to the store and made them try connecting the phone to one of their laptops, if course everything worked perfectly there
So now im back trying to figure out what to do. Going to find the post you mention and see if I get any hints there.
Did you notice my post above where you I claimed you can root and unlock without the drivers?
What do you need to do that you need them?
Hi,
I am reading this, it is exactly what I recognize with my new One X+ too.
BUT I am not wanting to root or something. I'd like the Navigon software to recognize my device and download the maps like it did on my Desire HD.
Any more hints to how I can get this running ?
regards,
Ruud
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Toggle debugging on then off.
I am in the same boat as you. A suggestion was posted in my thread in the Q&A section that PDANet solves the issue as it installs the drivers for you but it didn't work for me. Any dev's know a solution to this issue.
"fastboot devices" should work.
orangechoochoo said:
"fastboot devices" should work.
Click to expand...
Click to collapse
mine does it gives me the serial number and fastboot
but neither of our adb devices work.
I did the USB Debugging toggle multiple times and and it won't work. I saw your thread termin8tor22 and I am in the process of trying the pdanet solution. I'll post back if it works for me.
orangechoochoo said:
"fastboot devices" should work.
Click to expand...
Click to collapse
When you say that it should work, are you referring to the fact that we can run the exploit and unlock the phone even though it doesn't show in adb devices? I haven't been able to get mine to work that way. Thanks.
The pdanet didn't work either same error as previously stated. Mine doesn't even show up in fastboot devices. I am at a total loss here. I tried to override the drivers and it fails and states that the MTP USB Drivers are the most up to date and refuses to change or update it.
antnyh said:
When you say that it should work, are you referring to the fact that we can run the exploit and unlock the phone even though it doesn't show in adb devices? I haven't been able to get mine to work that way. Thanks.
Click to expand...
Click to collapse
No, the exploit will not work if your phone does not show up in adb.
Also, this thread should be in Q&A, not in Development.
antnyh said:
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Click to expand...
Click to collapse
I was able to get it to see the device after going into cwr. then i was all good
jsa11ey001 said:
I was able to get it to see the device after going into cwr. then i was all good
Click to expand...
Click to collapse
How can we get cwr whithout an unlocked bootloader or root. This isn't helpful unless we have cwr already on there which we don't as we don't have root because we don't have adb to push the exploit. I don't mean to be rude but I am getting aggravated with this ADB thing.
CastleBravo said:
No, the exploit will not work if your phone does not show up in adb.
Also, this thread should be in Q&A, not in Development.
Click to expand...
Click to collapse
The thread is where it is unless a mod wants to move it.
jsa11ey001 said:
I was able to get it to see the device after going into cwr. then i was all good
Click to expand...
Click to collapse
I am trying to unlock it so I can get CWR on it. I can't even unlock it since it refuses to show up in ADB. How did you get CWR on yours if you don't mind me asking?
antnyh said:
The thread is where it is unless a mod wants to move it.
I am trying to unlock it so I can get CWR on it. I can't even unlock it since it refuses to show up in ADB. How did you get CWR on yours if you don't mind me asking?
Click to expand...
Click to collapse
I pushed thru adb. did you uninstall htc sync and update your android sdk. sorry just trying to give any usefull info. not in any way a master dev or anything
---------- Post added at 06:43 AM ---------- Previous post was at 06:35 AM ----------
i used this method http://forum.xda-developers.com/showthread.php?t=1996389, and had to do the CIDGEN unlock because I have a verizon phone. I followed the steps exactly and had 0 problems.
see you pushed through adb, which we cant get to recognize our devices. thats all, no harm intended.
antnyh said:
The pdanet didn't work either same error as previously stated. Mine doesn't even show up in fastboot devices. I am at a total loss here. I tried to override the drivers and it fails and states that the MTP USB Drivers are the most up to date and refuses to change or update it.
Click to expand...
Click to collapse
did you change your environment variable path set to your adb/fastboot location?
As for the drivers:
HTCDriver.RAR > run the exe
HTCDriver.rar
HTC.RAR > put in C:\Program Files\ and C:\Program Files (x86)
HTC.rar
thats my setup and it worked
antnyh said:
As the title states when I run adb devices it returns an empty list. I have USB Debugging on. I am at a loss here. I have also uninstalled the drivers and tried to push the Google drivers in SDK. That still didn't work. Any advice would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
I had similar issues with ADB not recognizing the DNA, I disabled HTC sync and closed out of the HTC SYNC in the task manager... You may or may not have tried this... Based on my experience this was what happened with me.. I also have windows 8 64bit. Hope this helps
:fingers-crossed:
I installed drivers listed on one of the forums here. then i installed htc sync. Then i had to download the sdk /with google drivers.
I would assume that when you have your command prompt open that you cd into the folder. platform-tools. that way the cmd can find adb?
kraziekc said:
Hello,
I had similar issues with ADB not recognizing the DNA, I disabled HTC sync and closed out of the HTC SYNC in the task manager... You may or may not have tried this... Based on my experience this was what happened with me.. I also have windows 8 64bit. Hope this helps
:fingers-crossed:
Click to expand...
Click to collapse
Hmm.. I haven't started mine yet but I'm on win8, this seems like good advice. Will be trying later and post results
Sent from my HTC6435LVW using Tapatalk 2
damagickid said:
I installed drivers listed on one of the forums here. then i installed htc sync. Then i had to download the sdk /with google drivers.
I would assume that when you have your command prompt open that you cd into the folder. platform-tools. that way the cmd can find adb?
Click to expand...
Click to collapse
If you set up adb right you don't have to CD into that folder.
Sent from my HTC6435LVW using xda app-developers app
You need to disable HTC Sync. Go in task manager and see if there is another ADB current running. That is what happened to me, HTC Sync was trying to push via ADB so when I tried to root it couldn't recognize my DNA.
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
Click to expand...
Click to collapse
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
[TSON] said:
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
Click to expand...
Click to collapse
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
inexplicability said:
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
Click to expand...
Click to collapse
Ran into this yesterday. My computer ONLY has USB3 so I was unable to get it to work. Tried on a Win7x64 machine and did it first time no problem. Sigh...
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I don't have any tips for you, other than to say that I've had fastboot work with my DNA on 2 different win 8 64 machines.
I *think* I got my drivers from HTCSync, and then uninstalled HTCSync, but not the drivers afterwards.
I did have problems with fastboot and adb when I was playing around with the CM10 build that is available here. Maybe try switching your rom and kernel?
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I ran into the same exact issue on my win8 64-bit machine. luckily i have a couple usb2 ports and they work just fine. i wonder if using a usb hub that is compatible with usb2 or lower would work.
Did you try disabling driver signing in Windows 8 pretty sure thats the problem.
Here
Yeah you have to do that in order to install the universal driver or any other unsigned drivers - but once the drivers are installed you're good to go. No matter which drivers I pick I have this problem, I've tried probably 7 different ones.
Works fine on my Vista laptop but that things about to creak... Just used it to S-OFF and it took over an hour to turn on :crying:
EDIT: And for what it's worth, doesn't matter if it's a USB 3.0 or 2.0 - same error. Doesn't work on stock or on Cubed/Viper (though this is fastboot so kernel/ROM shouldn't have anything to do with 'em).
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
1stx2 said:
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
Click to expand...
Click to collapse
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
travisn000 said:
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
Click to expand...
Click to collapse
It's absolutely crazy isn't it? Please let me know if you figure out the problem. I don't consider myself a noob about rooting/romming/etc but this is making me feel like i just started today!
EDIT:::: I finnally got my phone to connect to my moms laptop but it still wont connect to mine. I got CASUAL to recognize the phone but I'm kind of scared to do it now since my first phone connected perfect the first time and when I started having other problems and needed to send it back and usb debugging WOULD NOT work. I don't want to leave it stock but I don't want to go through what I went through with the first phone again
Ok, I finally got my phone rooted, unlocked using casual. I had to use my moms laptop ( hp, windows 7, 32 bit ) to unlock it, our desktop ( windows xp 32 bit ) to use odin and my laptop to transfer music, vidoes, etc..... Now i absolutely hate installing drivers and windows in general. You would think being 1 of the top-of-line smartphones, **** like this wouldn't be so difficult.
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
travisn000 said:
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
Click to expand...
Click to collapse
Yep that's the same thing that happened on my windows xp based desktop, it would boot into download mode but it wouldn't recognize the phone. It's got to be a driver related issue though. I had similar issues with my gnex but that was nothing compared to this catastrophe.
Sent from my SCH-I605 using Tapatalk 2
I finally got mine done.. gave up on windows drivers and went back to linux.
I had to switch to a disto that used gksudo & dpkg in order for the CASUAL app to work properly (..my distro of choice is PCLinuxOS, but it doesn't use gksudo or dpkg).
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
jonathan413 said:
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Did you try closing HTC Sync Manager?
Make sure and exit completely, right click and exit in the system tray
Yeah I've tried that. I think I've done everything and adb/toolkit will not read my phone but everything else is and all drivers installed perfectly. I'm just at a loss. Mostly all androids I've had have all been read quickly especially my last phone the note 3
Sent from my HTC One_M8 using xda app-developers app
jonathan413 said:
Yeah I've tried that. I think I've done everything and adb/toolkit will not read my phone but everything else is and all drivers installed perfectly. I'm just at a loss. Mostly all androids I've had have all been read quickly especially my last phone the note 3
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Not sure it would matter since you're running commands from ADB but did you turn off fast boot in the power options? Also, I know there's a tool somewhere here on XDA where you can remove all of the android drivers and start fresh. I want to say it's called USBDeview. It was part of the WugFresh nexus 10 toolkit. I used the tool to get rid of all my samsung drivers and also HTC drivers so I could start fresh
Here's a link to the toolkit. Try using the driver installation guide there, it has the tool in it I used to get rid of all the android devices to start fresh.
http://forum.xda-developers.com/showthread.php?t=2015467
This is assuming your drivers are the problem which is what it sounds like
Edit: just use that toolkit for the USBDeview tool, not to unlock your device as it is for the nexus 10. Lol sorry had to just make sure
TheEmpyre said:
Not sure it would matter since you're running commands from ADB but did you turn off fast boot in the power options? Also, I know there's a tool somewhere here on XDA where you can remove all of the android drivers and start fresh. I want to say it's called USBDeview. It was part of the WugFresh nexus 10 toolkit. I used the tool to get rid of all my samsung drivers and also HTC drivers so I could start fresh
Here's a link to the toolkit. Try using the driver installation guide there, it has the tool in it I used to get rid of all the android devices to start fresh.
http://forum.xda-developers.com/showthread.php?t=2015467
This is assuming your drivers are the problem which is what it sounds like
Edit: just use that toolkit for the USBDeview tool, not to unlock your device as it is for the nexus 10. Lol sorry had to just make sure
Click to expand...
Click to collapse
well thats the problem. ADB isnt recognizing the phone but the rest of the computer is.
jonathan413 said:
Hey guys I'm trying to unlock the boot loader through the all in one toolkit but it keeps saying device not find! All drivers installed correctly and the phone is being picked up through mass storage and connects to computer fine. I also have sdk tools installed and HTC drivers installed but the tool kit still didn't find phone. Also I run ADB devices and it didn't show up. Any ideas?
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
umm, did you enable developer options and enable usb debugging? if you type adb devices and nothing shows up, its not going to work. You should learn how to do it all manually anyways. It could save you in the future. Go to htc dev site and it walks you through it for windows and mac. VERY easy. You need to learn to use fastboot commands. Msg me if you can't get it done.
jonathan413 said:
well thats the problem. ADB isnt recognizing the phone but the rest of the computer is.
Click to expand...
Click to collapse
Right, and I guess I'm saying that it may be worthwhile to try cleaning out your drivers and then starting from scratch with HTC driver and android interface driver. When I cleaned out mine I had several duplicated. After removing them I was able to connect to my device just fine. I can't think of another reason why your device wouldn't connect
an0ther said:
umm, did you enable developer options and enable usb debugging? if you type adb devices and nothing shows up, its not going to work. You should learn how to do it all manually anyways. It could save you in the future. Go to htc dev site and it walks you through it for windows and mac. VERY easy. You need to learn to use fastboot commands. Msg me if you can't get it done.
Click to expand...
Click to collapse
ive never had any problems with command ADB DEVICES showing the connected device until this phone. I CANT use htcdev because it makes me download some file called "fastboot-win.zip" and after extracting it wont opne and gives me error message of some missing file which is indeed not missing. And dont you need ADB when you get the unlock token anyway? never had this type of issue before.
TheEmpyre said:
Right, and I guess I'm saying that it may be worthwhile to try cleaning out your drivers and then starting from scratch with HTC driver and android interface driver. When I cleaned out mine I had several duplicated. After removing them I was able to connect to my device just fine. I can't think of another reason why your device wouldn't connect
Click to expand...
Click to collapse
there is no other drivers showing up other than HTC's. and ive reinstalled it at least three times. everything is working except ADB recognizing the phone.
jonathan413 said:
ive never had any problems with command ADB DEVICES showing the connected device until this phone. I CANT use htcdev because it makes me download some file called "fastboot-win.zip" and after extracting it wont opne and gives me error message of some missing file which is indeed not missing. And dont you need ADB when you get the unlock token anyway? never had this type of issue before.
Click to expand...
Click to collapse
You must enable usb debugging to use adb on htc. go, settings, about and click on build like 10 times until it says developer options, then go to settings/developer options and turn on debugging. adb will not work on stock rom unless you do this.
Do you have the fastboot application in addition to the ADB application in the directory from which you are running commands? You absolutely need fastboot to get your unlock token.
Also just to clarify, what exactly does it say when you try to run ADB commands? Simply "device not found?"
an0ther said:
You must enable usb debugging to use adb on htc. go, settings, about and click on build like 10 times until it says developer options, then go to settings/developer options and turn on debugging. adb will not work on stock rom unless you do this.
Click to expand...
Click to collapse
thats already checked. just unistalled all duplicate drivers and started fresh. now there is 3 drivers not installing. CDC serial, Android phone, and CDC serial again. not sure why that one installs twice but it failed anyway..those 3 will not install for the life of me.
TheEmpyre said:
Do you have the fastboot application in addition to the ADB application in the directory from which you are running commands? You absolutely need fastboot to get your unlock token.
Also just to clarify, what exactly does it say when you try to run ADB commands? Simply "device not found?"
Click to expand...
Click to collapse
in the toolkit it says "device not found"..when i run ADB devices it says "list of devices" but shows nothing. Now when i run the command it says in missing some .DLL extension file
Reboot your computer, install HTC sync manager again, then plug in your phone and drivers should install properly. But of course uninstall or close sync manager before you start running commands again
newest adb? usb 2 port? I have a mac so its a little different, but i had to update my adb when kit kat came out.
TheEmpyre said:
Reboot your computer, install HTC sync manager again, then plug in your phone and drivers should install properly. But of course uninstall or close sync manager before you start running commands again
Click to expand...
Click to collapse
ok i followed your instructions and yes all the drivers installed correctly, thank you. BUT now i run the toolkit and now it says "error: device offline".
an0ther said:
newest adb? usb 2 port? I have a mac so its a little different, but i had to update my adb when kit kat came out.
Click to expand...
Click to collapse
not sure. i dont keep ADB on my computer. I download it only when I need to. But i followed the instructions from the other user but now i get this message. "error: device offline".
Do you get the same result when you run 'adb devices' in command prompt? Also uncheck verify apps and unknown sources in security. And I just want to make absolute certain you have usb debugging enabled once more
TheEmpyre said:
Do you get the same result when you run 'adb devices' in command prompt? Also uncheck verify apps and unknown sources in security. And I just want to make absolute certain you have usb debugging enabled once more
Click to expand...
Click to collapse
ok so i ran the toolkit for the 3rd or 4th time and it rebooted in fastboot to obtain my token to unlock. but when i enter the token into htcdev website it keeps saying its wrong length. i checked over and over and its the right length and im copying what i see from the htc dev website instructions but three times i get wrong token length.
ok i got the code to work..now onto the next step.if i have problems ill be back here.