Hello,
I haven't dealt with HTC since my original Desire and I'm now trying to root this 816 for a friend. I must be missing something because I've been to this all day
The problem is that I cannot unlock the bootloader as to the instructions in HTCdev. The command fastboot oem get_identifier_token does not work and returns FAILED (remote: unknown command)
I've tried this on two different PCs without success. The device gets recognized in both ADB and fastboot.
As I've understood, I have to get past this first step or otherwise there's little to do. Any suggestions?
Thanks!
you should preferably uninstall hTC sync(but not remove hTC drivers), also have USB debugging enabled in developer options.
also, try using the tools from here
seekfind said:
you should preferably uninstall hTC sync(but not remove hTC drivers), also have USB debugging enabled in developer options.
also, try using the tools from here
Click to expand...
Click to collapse
On the other PC I do not have HTC Sync even installed. I've also tried with different drivers (Google, HTC Android Interface...) but the result is always the same. USB Debugging is enabled, but in fastboot it shouldn't make any difference, as far as I know you cannot toggle it on or off.
Edit: I'm actually using the minimal ADB and Fastboot.
HTC Sync is good!
Actually, install HTC Sync Manager. It comes with the needed drivers and even adb and fastboot, so you should try it. As far as I know the adb and fastboot are located somewhere in the folder where you installed the sync manager
Related
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
JT-on said:
Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
Click to expand...
Click to collapse
To use ABD you need to be connected in recovery or a booted device.
nlooooo said:
To use ABD you need to be connected in recovery or a booted device.
Click to expand...
Click to collapse
Brilliant. Like you said, ADB recognized my device in both booted OS and recovery. However, I needed to be in recovery to push files to the system directory. Thanks.
You're welcome. You can push in booted device you just need to enable superuser rights in adb shell.
Sent from my HTC Desire using Flashes and Thunders
JT-on said:
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
Click to expand...
Click to collapse
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
rmp5s said:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
Click to expand...
Click to collapse
You can't. Both the n4 and the n7 have their memorys formatted as ext4, partition type that windows can't access normally. MTP was the only sollution google had.
Hi,
I am trying to unlock the boot-loader for HTC one V using the steps given on their official website
followed all the steps, but when i reach step 8: and type in
>fastboot oem get_identifier_token
It just shows waiting for devices, whereas my device is already connected. and in the FASTBOOT mode
When I type
>fastboot devices
It shows nothing (should'nt It show the device which is already connected?)
I have the Android SDK installed and copied the 3 required files from the Platform-tools folder.
ie -
adb.exe
AdbWinApi.dll
fastboot.exe
I have the USB debugging turned on,
HTC sync manager is installed and it also shows that the Driver is up-to-date.
Though, when I plug in the Phone in Fast Boot mode it shows USB device not recognized.(I am using Windows 8 Pro )
This Is the first time I am trying this
What am I doing wrong? any help would be appreciated.
TIA.
srivassumit said:
Hi,
I am trying to unlock the boot-loader for HTC one V using the steps given on their official website
followed all the steps, but when i reach step 8: and type in
>fastboot oem get_identifier_token
It just shows waiting for devices, whereas my device is already connected. and in the FASTBOOT mode
When I type
>fastboot devices
It shows nothing (should'nt It show the device which is already connected?)
I have the Android SDK installed and copied the 3 required files from the Platform-tools folder.
ie -
adb.exe
AdbWinApi.dll
fastboot.exe
I have the USB debugging turned on,
HTC sync manager is installed and it also shows that the Driver is up-to-date.
Though, when I plug in the Phone in Fast Boot mode it shows USB device not recognized.(I am using Windows 8 Pro )
This Is the first time I am trying this
What am I doing wrong? any help would be appreciated.
TIA.
Click to expand...
Click to collapse
Run the SDK Manager, do you have the Google USB Driver installed (it's under extras). I'm not 100% certain but I think you need to install that to recognize the phone in Fastboot mode.
-Duir- said:
Run the SDK Manager, do you have the Google USB Driver installed (it's under extras). I'm not 100% certain but I think you need to install that to recognize the phone in Fastboot mode.
Click to expand...
Click to collapse
Hey, Thanks for your reply, I had the Driver installed already, but there was some problem with Usb3.0 i guess
I plugged the device in Usb2.0 port and followed the steps and It worked Fine.
:good:
Hi Guys
Ive installed Cyanogen 10.1 on m HTC One X all went fine no issues with install etc. However since I have installed im unable to get my PC to identify my htc one x for an ADB connection. I have updated all software from SDK Manager its no longer asking for downloads however the device is never found by ADB. I used the all in one toolkit to root and install the rom but this is now coming up with the same error. I have read that some phone need an edited driver once updated to cyanogen 10.1 does anyone have the modified inf file for the one X all i can find is one for the Samsung which doesnt work I already give it a shot .
Any help appriciated as i spend a good few hours trying to work this one out last night.
You have to enable USB debugging and allow ADB in developer options... Both are by default disabled on CyanogenMod
desmond1303 said:
You have to enable USB debugging and allow ADB in developer options... Both are by default disabled on CyanogenMod
Click to expand...
Click to collapse
Hi Mate
Thanks for the responce sorry should have said I have already enabled Developer Options within Cyanogen and have enabled usb debugging and the new one required for 4.2 which is ADB over network but ADB still still error no device found. Its seem to be something to do with the driver as I originally used the HTC drivers to flash and now I have a generic rom i.e. not one configured by HTC the PC doesnt appear to correctly identify the device. I have reinstalled the drivers a numbr of times and have also tried using the Google driver but my PC states this is not correct for the device and refuses to install it.
Well... I have the stock HTC drivers and they work for every single rom I have tried yet, weather AOSP or Sense...
Have you tired a different PC ?
You given adb root access in dev options?
Sent from my HTC One X using xda app-developers app
treebill said:
You given adb root access in dev options?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi Mate
Thought I had enabled all the options but possibly found the issue. I had enabled USB debugging and ADB over network but hadnt amended the root access to have apps and ADB enabled. Im in work at the mo so cant test but will def check this out as soon as I get in later. Hopefully that will sort it thanks for the assist guys will report back later to cofnirm either way.
Hi Guys
Sorry same issue I have enabled the root access for ADB aswell as apps now my PC is identifying the phone have tried adb when phone installed as My HTC and also installed with HTC Android Interface however adb still isnt detecting my phone when connected. Any Ideas would be great
does fastboot work ?
if you type in fastboot devices wile in fastboot usb mode, what does it say ?
desmond1303 said:
does fastboot work ?
if you type in fastboot devices wile in fastboot usb mode, what does it say ?
Click to expand...
Click to collapse
Yeah seems ok shows
Phone Name Fastboot
Im sure its a driver thing as ive been installing drivers manually and now i can get the phone to read in adb but it errors as offline like
Phone Name offline
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed
I was having issues with adb not finding my device. These drivers worked for me...
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app
Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all
confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless
If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2
I just bought a new computer yesterday, after installing the lightweight adb/fastboot program to my dell inspiron windows 8.1 laptop. I realized when I try to see the devices connected to adb by the command : adb devices, the only that pops up is list of devices attached, but show nothing. Here's the guide I followed http://forum.xda-developers.com/showthread.php?t=2778239
I'm guessing it has something to do with the drivers.....any help appreciated......
Here's the link I used to installed minimal adb and fastboot http://forum.xda-developers.com/showthread.php?t=2317790
Try uninstalling HTC Sync and any HTC drivers, then try to re-install, and see if that helps.
If no, uninstall any HTC software and drivers. Connect phone, go to Device Manager, and see if the device shows up. If so, select the option to manually select drivers (ignore any prompts to automatically install HTC Sync, etc.) and pick the Generic Android MTP drivers.
See if that works, although Win 8.1 has been known to be more problematic connecting to this device than previous Win builds.
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
I've already switched cid yo gpe cod, but I'm probably going yo switch to dev edition
jxcorex28 said:
Well I finally got it to work..I never installed the HTC sync software. I found a good link of compatible drivers for my 8.1. I didn't realize the phone had to be in bootloader mode to use fastboot commands though. That's a new thing forbme. If I remember correctly, I could use fastboot commands while the android was in its GUI/ROM format...
Click to expand...
Click to collapse
Fastboot commands only work in fastboot mode. Its always been this way.
adb commands work in the OS or recovery, but not in bootloader or fastboot.
For some reason I was thinking the opposite...god, I'm retarded. I went ahead,and downloaded the entire SDK anyhow. Everything's up to speed