Database Develop

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

[HELP] I replaced my HTC One Launcher And Now I Think I bricked It

please delete thread
deleted

good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)

jcwxguy said:
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
Click to expand...
Click to collapse
...what he said, or just use the RUU to go back go stock.
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Either way it sounds like you'll be just fine but make sure there's juice in your battery before trying any of the solutions.

ADB Can't find the device :/
deleted

Wipe and reflash rom
Sent from my HTCONE using Tapatalk 4 Beta

raphyv23 said:
I tried to sideload it but adb would not recognize my HTC One. I have installed the drivers correctly on Windows 8 and its recognized as Android ADB Interface under Android Devices on my device manager. when i type adb devices on adb it doesnt come up with anything. I also tried using my Windows 7 Laptop but the drivers wont install on windows 7
Please help :/
Click to expand...
Click to collapse
your cmd window needs to be in the folder with the adb tool, normally something like c:adroid sdk\platform tools navigate to this directory in windows explorer the hold shift and right click on and empty part of the window and select "open command prompt here"

Still wont work
deleted

raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
{
"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"
}
Click to expand...
Click to collapse
in your recovery, when your in advanced, did u swip to start sideload? even if it doesnt recognize it, try to sideload a rom anyways, should give u a %

raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
Click to expand...
Click to collapse
are you running as administrator, try typing after that adb reboot bootloader and see what you get
another thing are you using a 3.0 usb port??

It worked thank you
deleted

[Q] Can't get MTP to work

Hi,
I have been trying to connect my Nexus 6 to my work pc but I just can't get the MTP file copying mode to work properly. I have used the latest Google USB driver and actually it's not so bad. With USB Debugging turned ON, I see "Android Deivce > Android ADB Interface" properly installed in device manager. I even see my phone's serial no. when I type "adb devices" in command prompt. BUT the bloody MTP mode just refuses to work. It keeps showing up in Device Manager as "Other devices" > MTP, with a question mark next to it.
{
"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"
}
When I switch USB debug off, there's no Android ADB Interface, and the unknown MTP entry in "other devices" transforms to "Nexus 6", again with a question mark next to it.
I have tried to manually install the proper driver but for starters, if I just select the folder where the .inf files are located Windows don't seem to anything inside it and when I force it to use that file ("Show All Devices > Have Disk") it only shows ADB and Bootloader drivers:
So what am I suppose to choose there in order for MTP to work as it should?

Have you tried other pc or laptop??

Yes, the phone shows up correctly in all modes on my home pc.

Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ

DebianDog said:
Just for giggles you ought to download the Nexus toolkit and let it go find the drivers it thinks it needs to work. afterwards you could just delete the tool. http://www.wugfresh.com/nrt/
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I did that to no success but in the end, I just tried a different USB2.0 port and it worked, all drivers installed correctly. Now the weird thing is I can read from the internal memory of the phone, I can delete stuff from it, but when I try to copy something to it it says: "Error copying. The device has either stopped responding or has been disconnected" so I can't yet copy to it. This is driving me crazy right now...

I have this issue this morning. Right click and Update Drivers > Browse For Drivers > Let me pick > Portable Devices > Standard MTP Device > MTP Device.

BL unlock win10 pro

Hi there,
I have a E6335, isn't there released adb drivers for windows 10 pro x64?
I've used the "Minimal ADB and Fastboot" pack from here, and i can get it to reboot through ADB, but after that it isn't recognized, so i have to perform a hard reboot throug the button beside the sim.
Im not that familiar with adb and fastboot, so if anyone could guide me, i'll be very thankful.
Kind regards.

driver signed in Windows 10
Try this:
http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
... and tell us if it works (should with the proper drivers from SONY's developer site).

Hi there,
It dosn't work.
Genuine drivers was installed, but i did a reinstall, same problem, the S1 Fastboot driver is not installed.
Drivers works fine, until i perform the "adb reboot bootloader" command in adb, after that, the fastboot driver is unknown in device manager.
I've tried to perform the unlock command afterwards, but it keeps hanging on the "waiting for device".
Performing the "fastboot devices" dosn't work.
{
"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"
}
I guess i have to go on a win7 machine then?
Thanks.

I guess i have to go on a win7 machine then?
Click to expand...
Click to collapse
I recommend Debian Jessie
Read Androplus's advice. http://forum.xda-developers.com/showpost.php?p=62577784&postcount=2
I see the wrong command in your screenshot.
You know how to get into fastboot mode?
Power off the device. Hold "Volume up" (until the LED turns blue) and plug in USB cable.
I do not know, what you are up to with unlocking the bootloader but if these first steps go so badly you better stop here before attempting to root the device or doing something else. You could end up with a brick.

reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.

I'm not a newb in droid phones, just the adb. And i've just used the commands from this thread: http://forum.xda-developers.com/xperia-z4/general/bootloader-unlock-tip-t3165018
And if thats wrong, i think that it should be corrected.
And same issue as the before mentioned, when i use the vol up option.
@monx
I'll try that right away. I've just updated all 6 machines to win10 from 7, so im not that familiar with it yet

reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
Click to expand...
Click to collapse
That did the trick, thank you buddy

Question [FIXED] fastboot.exe/Mi Unlock Tool won't recognize my device

Hello!
I wanted to unlock my bootloader on my Redmi Note 11, but I have ran into a problem. It won't detect it in fastboot.exe or the Mi Unlock tool. I already:
Installed the Google USB driver
Updated the Mi Unlock tool, My phone, Windows
Enabled USB debugging & OEM unlocking
Booted the device in fastboot mode (Orange text saying FASTBOOT)
Can anyone help? Thanks.
{
"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"
}

Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?

ze7zez said:
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
Click to expand...
Click to collapse
Thanks for your reply
The cable is in perfect condition, it was shipped with my phone and it works.
No I am using the one on the case, I am not sure on how it will affect this in any way but I am gonna try it.
Nope, ADB doesn't report anything

yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh

Thunderoar said:
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Click to expand...
Click to collapse
Thank you, I forgot to mention I already fixed this.

_matteodev said:
Thank you, I forgot to mention I already fixed this.
Click to expand...
Click to collapse
can you mention how you fixed it? i'm having the same problem