Database Develop

HTC Touch Diamond Won't connect to PC.

Alright, I'm running Windows 7, and this is exactly what happens.
First, i connect my HTC Touch Diamond, on the phone screen it asks me to choose ActiveSync or Disk Drive, regardless of what i choose, or if i choose none, i always instantly get the following error appears in the task bar and the "Unknown Device" in device manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Under the devices properties in Device Manager, the Device Status says "Windows has stopped this device because it has reported problems. (Code 43)".
If i try re-running the Windows Mobile Device Center installer (drvupdate-x86.exe from http://www.microsoft.com/downloads/...F1-E46A-4A5F-A791-09F07AAA1914&displaylang=en) the following happens:
So, apparently it finds the driver and then attempts to install it, but while doing so, the device appears to become 'unplugged' some how and then the Windows Mobile Device Center installer continues on its way.
I've tried various reported fixes for problems like this, such as:
-Checking or unchecking the "Enable advanced network functionality" box in Start->Settings->Connections->USB to PC.
-Used 2 different cables in various USB ports.
-Deleting the device from device manager, resetting my PC and soft resetting my device then reconnecting them.
-Hard and soft resetting the device
-Enabling various system services, such as the UPnP one (which was originally disabled for some reason)
-Tried it on an XP machine, same task bar error, and same Unkown Device in Device Manager.
None of the above has worked, and im out of ideas. I'd be extremely grateful to anyone who could help out, i've tried to provide as much information as possible, if anything else is needed, just ask.
Thanks in advance.
/-- Aleid.

could anyone help? or atleast point me in the right direction?

Aleid said:
could anyone help? or atleast point me in the right direction?
Click to expand...
Click to collapse
I've got the same problem, and haven't figured it out, yet

Check this link here: http://www.we-u.com/?p=1321
I've just found it and trying it out right now, but it looks like it would work

Just find the drivers on the net and install them manually, then try n connect

Solution?
Hi!
I have the same problem with a HTC Touch HD. Can you tel me what is the solution?
Thx,
Darknight

hi, i have a same problem. i am using a standard 5 pin mini usb which comes with nokia n95.
Please tell me is it right to use 5 pin usb cable or i have to buy 11 pin mini usb cable.
my touch diamond starts charging when plugged 5pin mini usb but doesn't sync.
plz help

I'm having the same issues as the OP. I'm thinking if I could manually load the drivers, all would be well. Could someone who DOES have it working with Windows 7 perhaps strip the driver out somehow and post it here? I've tried all of the tricks listed above, with no luck. I'm going to try to get it working with my laptop running XP later tonight... maybe I can find the driver that way?

try this.
i also had this problem. try another data cable which ur friend use to connect his htc.

same problem, and it causes errors connecting as flash memory.
tried same computer, same cable, but windows xp sp3 with activesync. everything worked fine.
wtf is wrong with windows 7?

ms-dos said:
same problem, and it causes errors connecting as flash memory.
tried same computer, same cable, but windows xp sp3 with activesync. everything worked fine.
wtf is wrong with windows 7?
Click to expand...
Click to collapse
there is nothing wrong with windows 7, I think you need WMDC 6.1 Driver for Windows Vista (64- bit) to make it work
in this site you can get it http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3182

I have a problem with my diamond, can't make it work through usb with my pc.
It gives me an error in device manager:
"Windows has stopped this device because it has reported problems. (Code 43)".
I have installed wmd and tried different usb ports with no luck.
On my pc I have win10 installed, any suggestions?

Hi,
not sure if HTC Diamond can sync with Windows 10. I run Linux and have Windows XP with ActiveSync in VirtualBox. Works fine. So you may want to try the same, run XP in a Virtual Machine under Windows 10.

ADB Driver - Access is Denied

So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
HTC ADB Composite Device Driver (not sure exactly of this...)
Access is Denied
Click to expand...
Click to collapse
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.

Stigy said:
So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.
Click to expand...
Click to collapse
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess

xidominicanoix said:
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess
Click to expand...
Click to collapse
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.

Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around

http://forum.xda-developers.com/showthread.php?t=532719
The link in this thread usbdeview seems to fix alot of driver issues

Stigy said:
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.
Click to expand...
Click to collapse
i got mines from the 1.6 sdk .. x64

Simple Solution
Here is a simple solution without having to read that long thread:
For future reference, here is how to install the drivers or fix the drivers should they not be working.
Everything you need is contained within this:
http://www.divshare.com/download/8845496-f72
This is the howto documentation
This is how to get your android phone to connect to you PC
to use functions like adb and other developer tools.
If you have installed the phone before but adb function dont work
then:
1) Run USBDeview
2) Select the list item(s) that have the word "android" within the description
3) Right Click > Uninstall
If you have done the above, or are plugging your phone in for the first time:
1) Plug in phone
2 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
2 b) If no message appears or you get a message saying drivers failed
to install. Goto device manager
2 b i) start > All Programs > accessories > run
type devmgmt.msc and press ok.
3 b) find the android device in device manager, it will have a warning icon
next to it and be in a section like unknown.
4 b) Right click and install driver
5 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
Click to expand...
Click to collapse

USBDeview is awesome but....
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.

digimancer said:
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.
Click to expand...
Click to collapse
I have this same issue on an Ideos U8150 and on XP... At one point in the past it was working (before I flashed Cyanogen 7). Since then I have tried numerous driver packages, both specific to my phone and generic, and have had no luck getting past the access denied error.. I have even gone as far as changing the registry permission as well as checking all of my folder permissions... I am stumped.

Adb root - run that from command prompt.

B-man007 said:
Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around
Click to expand...
Click to collapse
I know it a while ago since you posted this but still, it helped me fix the "Access denied" thing which i didn't know how to fix. I installed ADB drivers 3 times... anyways, tnx :good:

So If you are like me you had this same issue in 2022. Idk if it will be a fix for you but it was for me.
follow this youtube video for the exact setup so you can get hopfully the same out com to the T.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. make sure you're in administrator mode for command prompt.
2. The file name has changed from what it was so instead of doing
cd adb\platform-tools_r30.0.4-windows\platform-tools
It's now this
cd adb\platform-tools\
This will get you to the correct path if you followed the file placement in the video.
next all you have to do is type
adb devices on the command prompt. to test if it worked
other things that you might have to try is seeing if the driver it self is being blocked. you might also have to turn off and back on developer mode. View other posts in this thread if it's still stuck for you. Hopefully I helped one person at least.

USB Drivers issue strikes again on Win7 x32 and x64 again...

I know there are many postings around for this as this is quite the common issue but i've read many of them and still can't get drivers to work for me on any Windows 7 machine... I have win7 x64 on a pc and win7 x32 on laptop and it's not working on either...
i' ve downloaded the newest drivers direct from the Samsung site and tried it on both...tried kies as well.. tried a few of the other drivers that i've found here and there but to no avail....
but its not completely failing....here's what i've got so far..
usb composite and usb mass storage install...with the newest samsung.. the only one that doesn't is the SGH-I897 drivers line...it never installs and stays red and no drivers stated...but i am able to connect to my phone via usb mass storage device... after i click it from the phone, then my pc or laptop will allow me to browse my phone and transfer files back and forth..even though the drivers for it aren't installed (at least on any screen that says they are working) but Kies will never detect the phone and if I want to MORE IMPORTANTLY run something like Odin... I can't connect...
so only usb mass storage connect to my phone from win7 x64 or x32 but that's it..i've tried different usb ports (as suggested many times).. tried a whole bunch of different drivers from every link i could find in this site and others..
the only thing i haven't tried drivers wise yet is the Galaxy S drivers for x64.. should i try those on my pc?
technically, if i can connect to my phone via usb mass storage and transfer back and forth (regardless of any supposed driver issues showing in win7) then shouldn't i be able to connect through a program such as Odin, etc?
I'm at a loss here and have tried a lot.. any other suggestions?

pchemerys said:
snip ... technically, if i can connect to my phone via usb mass storage and transfer back and forth (regardless of any supposed driver issues showing in win7) then shouldn't i be able to connect through a program such as Odin, etc? /...snip
adb interface detects as different hardware for the device, the mode is completely different. Not uncommon to have driver load on one and fight you on the other. even happens when it was working before.
Did you try Heimdall using the driver loader for it to manually change? then flash from there.
Click to expand...
Click to collapse

What rom are you using? Aosp roms (this includes ICS) require the google usb driver for your computer to recognize it with usb debugging enabled.
When you uninstall your drivers, are you deleting the folder in program files labeled Samsung?
The drivers that most people use, 32 and 64 bit, are in my sig link (for gb and previous roms).

this is so effing confusing.
I HAVE WINDOWS 7 64 Bit.
I HAVE NEVER HAD TO INSTALL DRIVERS.
I plug in the phone, and windows gets the drivers and installs them AUTOMATICALLY from the windows servers.
FFS...
here follow this guide i made and never worry about installing drivers again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mrhaley30705 said:
What rom are you using? Aosp roms (this includes ICS) require the google usb driver for your computer to recognize it with usb debugging enabled.
When you uninstall your drivers, are you deleting the folder in program files labeled Samsung?
The drivers that most people use, 32 and 64 bit, are in my sig link (for gb and previous roms).
Click to expand...
Click to collapse
I'm running the SGSICS rom R4.2 currently with Glitch Kernel v14 b5 on GB GT-I9000 Bootloaders... should those drivers you just mentioned work or something else?

TRusselo said:
this is so effing confusing.
I HAVE WINDOWS 7 64 Bit.
I HAVE NEVER HAD TO INSTALL DRIVERS.
I plug in the phone, and windows gets the drivers and installs them AUTOMATICALLY from the windows servers.
FFS...
here follow this guide i made and never worry about drives again.
Click to expand...
Click to collapse
You're lucky bud cuz i've tried...i'm on win7 x64 too and i too allow for win update to attempt driver download but to no avail.. you're the first i've seen who has posted saying this has worked for them... must be nice! lol

Hello there,
I know I have diffrent phone but I think this is the same problem I experienced before... It's rare but its a problem with windows 7.... Where windows can't recognize a plug n play device properly. I have this post in wacom forum... The solution was originally from Logitech forum... It seems it happens to any plug n play device... Hope this helps
http://forum.wacom.eu/viewtopic.php?f=4&t=8537
Sent from my HTC Sensation 4G with Beats Audio

pchemerys said:
I'm running the SGSICS rom R4.2 currently with Glitch Kernel v14 b5 on GB GT-I9000 Bootloaders... should those drivers you just mentioned work or something else?
Click to expand...
Click to collapse
Ics rom requires the google usb driver (aka nexus s driver) for usb debuggjng to recognize properly. To use the phone without debug, use Galaxy Nexus drivers. Both are in my sig link. The G Nex drivers are simple click and install. The google driver requires you to use device manager to specify the driver. You can google "how to install google usb driver" for detailed instruction.

[Nook HD+] Nook HD+ will not get out of MTP Device mode

I've been working with leapinlar in this thread
http://forum.xda-developers.com/showthread.php?t=1994129
to get my HD+ ready for sideloading and root. One thing to know up front is that I'm running with HD+ OS 2.0.2. I got to where the Nook shows up as a MTP Device (BNTV600 under Portable Devices in Win7 x64 Device Manager), but when I unplug the Nook, enable ADB, and plug it back in it keeps getting redetected as the MTP Device. I tried disabling and re-enabling multiple times, rebooting my PC, power cycling the Nook, different USB ports. Nothing seems to work. I used USBDeview to make sure there is nothing else with the same Vendor and Product ID installed (there isn't).
I have other BN drivers installed for my other Nooks (a Touch and Tablet). These have the same Vendor ID (2080) but different Product IDs. I don't think I should have to uninstall them, doesn't seem like that should be necessary.
The odd thing is, the first time I plugged the HD+ in to my PC ADB was accidentally already enabled. It was detected immediately as an Other Device as it should before installing the Android Composite driver. Once I disabled ADB and got MTP to install (and it does work - the HD+ is visible in File Manager) it will now never show up as a new Other Device with ADB enabled.
My apologies in advance, but I was hoping posting this in its own thread would maybe provide better visibility.

Per the NEW announcement,
http://forum.xda-developers.com/showthread.php?p=34819554#post34819554
I redeclare this thread open...

tonyp22 said:
I got to where the Nook shows up as a MTP Device (BNTV600 under Portable Devices in Win7 x64 Device Manager), but when I unplug the Nook, enable ADB, and plug it back in it keeps getting redetected as the MTP Device. I tried disabling and re-enabling multiple times, rebooting my PC, power cycling the Nook, different USB ports. Nothing seems to work. I used USBDeview to make sure there is nothing else with the same Vendor and Product ID installed (there isn't).
The odd thing is, the first time I plugged the HD+ in to my PC ADB was accidentally already enabled. It was detected immediately as an Other Device as it should before installing the Android Composite driver. Once I disabled ADB and got MTP to install (and it does work - the HD+ is visible in File Manager) it will now never show up as a new Other Device with ADB enabled.
Click to expand...
Click to collapse
I'm having the same problem. Were you able to get it working?
I think it has something to do with the OS being 64 bit and not being able to install the driver but it recognized it as an Android Composite Something once before I tried installing the driver on it and restarting but now it won't recognize it if I enable the developer option. It just keeps repeating the device disconected sound over and over and over OMG THE SOUND!
please let me know if you were able to fix it and how.
BTW, has ANYONE been able to get adb to work on win7 x64?

I had the same problem. I was able to fix it by going to the device manager and uninstalling the device listed under portable devices. Then when I unplugged and re-plugged in the HD, it showed up under Other Devices.

lkmiller said:
I had the same problem. I was able to fix it by going to the device manager and uninstalling the device listed under portable devices. Then when I unplugged and re-plugged in the HD, it showed up under Other Devices.
Click to expand...
Click to collapse
Didn't work for me.

r1c47 said:
I'm having the same problem. Were you able to get it working?
BTW, has ANYONE been able to get adb to work on win7 x64?
Click to expand...
Click to collapse
I've got it working with win7 64-bit and so does my husband.

Ok, I got it to work, somehow.
I'm not sure but here's what I think might have done it.
-with adb disabled connected the nook to the pc
-uninstalled device under portable device, it gets reinstalled automatically as BNTV600 under portable devices, again.
-restarted the nook and it's still recognized as BNTV600, without disconnecting it from the pc, enabled adb(which causes the pc to go into the annoying reconnect sound loop(now I noticed a usb mass storage device with the yellow yield sign with the exclamation mark so I decided to:
-click on the new device with the yield sign and select update device to install the device drivers for the adb(same as you would have tried normally before, just that this time it will work)
-check "adb devices" in command promt to make sure that it's being recognized
and that's pretty much what I think did it.
I think I've rooted it and enabled sideloading and disabled ota, I've yet to install any apps yet though. But there's this graphical glitch in the unlock screen which I think is a side effect from rooting(hope it isn't a glitch though...)
But yeah, I'm going to try installing an app now and will report back with my findings.

Thanks all for these suggestions. I had tried using various combinations of disbling / uninstalling but it never worked. I went to my Win XP Pro laptop and got it all hooked up in seconds that way.

r1c47 said:
Ok, I got it to work, somehow.
I'm not sure but here's what I think might have done it.
-with adb disabled connected the nook to the pc
-uninstalled device under portable device, it gets reinstalled automatically as BNTV600 under portable devices, again.
-restarted the nook and it's still recognized as BNTV600, without disconnecting it from the pc, enabled adb(which causes the pc to go into the annoying reconnect sound loop(now I noticed a usb mass storage device with the yellow yield sign with the exclamation mark so I decided to:
-click on the new device with the yield sign and select update device to install the device drivers for the adb(same as you would have tried normally before, just that this time it will work)
-check "adb devices" in command promt to make sure that it's being recognized
and that's pretty much what I think did it.
I think I've rooted it and enabled sideloading and disabled ota, I've yet to install any apps yet though. But there's this graphical glitch in the unlock screen which I think is a side effect from rooting(hope it isn't a glitch though...)
But yeah, I'm going to try installing an app now and will report back with my findings.
Click to expand...
Click to collapse
This worked great for me as well, thanks so much! I'm struggling to figure out how to use ADB to install an APK that I extracted from my phone. Aptoide worked for every app I wanted that I hadn't paid for in google play. But I have three apps I'd like to install that Aptoide does not have because they are paid apps. I'm stuck where I am trying to use ADB. All of the APK installers did not recognize the files if I just moved them to my nook from the computer. These are the files on my SD card. View attachment 4649607
The highlighted ones installed but the red circled one was a paid app and it did not even get recognized by the installer. I've gotten as far as getting my nook to be recognized in command prompt. I'm attempting to use command prompt to install the .apk but I think it may be a problem with the .apk itself. Do you know how to go about that? This is where I get stuck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My other struggle is that my nook also does not allow me to send anything to it. It connects. It's recognized but it will not allow files to go onto it.
I'm not sure what to do now. It doesn't let me type anything at this point and my nook doesn't even respond to the fact that I'm trying to send something to it. Please let me know if I'm doing it all wrong. I realize how green I am. I know this was forever ago for you so if you can't remember it's no biggie.

Getting ADB to work...

I have installed the Sony drivers. I did this while in test mode. The only error I get is that a driver called Sony Net did not install. I then downloaded the Android SDK tools and installed the Google USB driver. However, whenever I try to adb, I get the device is offline error. My cable has also been plugged directly into my PC instead of a hub but same error...
USB Debugging is enabled. In Device manager, I can see 'Xperia Z' under Portable Devices and 'Sony sa0107 ADB Interface Driver' under Sony Sa0107. What am I doing wrong?

sacredsoul said:
I have installed the Sony drivers. I did this while in test mode. The only error I get is that a driver called Sony Net did not install. I then downloaded the Android SDK tools and installed the Google USB driver. However, whenever I try to adb, I get the device is offline error. My cable has also been plugged directly into my PC instead of a hub but same error...
USB Debugging is enabled. In Device manager, I can see 'Xperia Z' under Portable Devices and 'Sony sa0107 ADB Interface Driver' under Sony Sa0107. What am I doing wrong?
Click to expand...
Click to collapse
HAve you ticked install from unknown sources in security? not sure if it will make a difference though?

xl VipeR lx said:
HAve you ticked install from unknown sources in security? not sure if it will make a difference though?
Click to expand...
Click to collapse
Yep, that's already ticked,

sacredsoul said:
Yep, that's already ticked,
Click to expand...
Click to collapse
Try
Unplug the usb and plug it back again in a different usb port.
Go to the Settings -> Applications -> Development of your device and uncheck the USB debugging mode and then check it again back!
Restart the adb on your PC. adb kill-server and then adb start-server
Restart your device and try again.

xl VipeR lx said:
Try
Unplug the usb and plug it back again in a different usb port.
Go to the Settings -> Applications -> Development of your device and uncheck the USB debugging mode and then check it again back!
Restart the adb on your PC. adb kill-server and then adb start-server
Restart your device and try again.
Click to expand...
Click to collapse
Really appreciate you trying to help! :good:
This is as far as I could go but the command doesn't actually happen. It doesn't reboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What do you get when you type adb devices
Sent from my C6603 using xda premium

xl VipeR lx said:
What do you get when you type adb devices
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Android>adb devices
List of devices attached
CB5A1P9WY3 offline

Still trying unsuccessfully to get it working. Don't know what else can be done haiz.

You tried googling?
Sent from my C6603 using xda premium

xl VipeR lx said:
You tried googling?
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Yep. Everything. Different cables, different port, rebooting both PC and phone, reinstalling ADB, updating ADB, nothing works.
Device is always offline. Maybe Win 8 x64 is just bad for this :crying:
EDIT : I am using the root with locked bootloader. Is that a problem? Does it need to be unlocked for adb?

Just a update. Interestingly enough, recovery for locked bootloader installs fine (after disabling and enabling USB debugging) but ADB still doesnt work.

adb does work, you connected to a shell on the device on the image above.
Download flashtool beta for xz and install it. There's a subdirectory drivers in the installation directory where you find an installer which installs adb, fastboot and flashmode drivers if you select the correct checkboxes.

schaggo said:
adb does work, you connected to a shell on the device on the image above.
Download flashtool beta for xz and install it. There's a subdirectory drivers in the installation directory where you find an installer which installs adb, fastboot and flashmode drivers if you select the correct checkboxes.
Click to expand...
Click to collapse
Thanks! Shall give it a shot.

This worked for me.
It's a a bit late but maybe someone can still use this info.
This link has instructions on how to setup the android usb drivers for XPeriaZ. Worked for me like a champ.
teamandroid dot com slash 2013 slash 02 slash 24 slash sony-xperia-z-usb-drivers-download
Happy coding!
Alberto