SOLVED! [Q] FLASHTOOL or ADB not working - Xperia Z Q&A, Help & Troubleshooting

Tried everything i can think of, fastboot works, but adb devices command shows no devices attached,
USB debugging is enabled and every time i plug the phone in, it recognizes it as Xperia Z MTP but does not prompt any installation of adb drivers.
Tried installing using the google usb driver, it shows up then as ADB interface but still not showing in adb devices.
Also installed flashtool
i just get the message
12/043/2013 01:43:49 - INFO - Device disconnected
12/043/2013 01:43:50 - INFO - Device connected with USB debugging off
12/043/2013 01:43:50 - INFO - For 2011 devices line, be sure you are not in MTP mode
But USB Debugging and install from unknown sources are both ticked
SOLVED CUZ AM DA VIPER!
added the following to the usb inf driver under amd64
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_5193
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_5193&REV0228
updated the driver manually on the Xperia Z under portable devices in device management,
After installing device showed up as sa07 adb interface or something like that
then clicked on update driver then clicked automatically search for the best driver and it is working
ROOOTED!

Hi mate, can you explain exactly where you put those lines of code in the inf, or could upload the inf file?
Having the exact same error -- rooted the phone, but can't get anything to recognise my phone in flashboot.
Cheers.

[email protected] said:
Hi mate, can you explain exactly where you put those lines of code in the inf, or could upload the inf file?
Having the exact same error -- rooted the phone, but can't get anything to recognise my phone in flashboot.
Cheers.
Click to expand...
Click to collapse
same issue and question like madmatt_315 above.. pls advise

what version or flashtool are you all using

@moheep help mine is xperia z3 D660e with locked bootloader and can't be unlocked same issue but it powers on but stuck on logo even charging same its soft bricked but flashtool gives same thing

xl VipeR lx said:
Tried everything i can think of, fastboot works, but adb devices command shows no devices attached,
USB debugging is enabled and every time i plug the phone in, it recognizes it as Xperia Z MTP but does not prompt any installation of adb drivers.
Tried installing using the google usb driver, it shows up then as ADB interface but still not showing in adb devices.
Also installed flashtool
i just get the message
12/043/2013 01:43:49 - INFO - Device disconnected
12/043/2013 01:43:50 - INFO - Device connected with USB debugging off
12/043/2013 01:43:50 - INFO - For 2011 devices line, be sure you are not in MTP mode
But USB Debugging and install from unknown sources are both ticked
SOLVED CUZ AM DA VIPER!
added the following to the usb inf driver under amd64
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_5193
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_5193&REV0228
updated the driver manually on the Xperia Z under portable devices in device management,
After installing device showed up as sa07 adb interface or something like that
then clicked on update driver then clicked automatically search for the best driver and it is working
ROOOTED!
Click to expand...
Click to collapse
Thank you for instruktions

Related

[Q] Android Compostite ADB device missing from Devices therefore no ADB

I'm trying to get adb shell work w OB, but no device is showing up after "adb devices" command.
There isn't any "Android composite adb device" in the device manager, only
"LGE Android Platform Composite USB Device" (does not work width the android sdk drivers).
- No "Other devices" present (Edit: There is a couple - all of them are Bluetooth related)
- Latest LG USB drivers installed
- USB debugging turned on
- tried all 4 usb ports
- Win7 32bit
Disclaimer> Did not found any Q&A Topic in Optimus Black sub-forum
Serval driver rei stall and phone reboot solved the issue.
Thread sould be deleted.
Sent from my LG-P970 using XDA App
having little bit different problem - i do have LGE Android Platform Composite USB Device in device manager. Driver says it's 2.2.0.0 from 30.11.2010 by LG Electronics Inc.
But adb can't find any devices.
edit:
usb debugging somehow has turned off

[Q] Android SDK tools error: device not found

I’ve got driver problem with my Incredible S. When I have the phone on normally and connect it with a USB cable it shows:
Android USB Devices / Android Composite ADB Interface
in device manager. However, when I go into fastboot USB mode it just shows
Android USB Devices / My HTC
and it won’t recognize the device with Android SDK tools.
I can run fastboot commands using the cmd prompt but when I run ADB commands I get device not found or similar messages.
I have a HTC One S phone and in fastboot mode it shows correctly
Android USB Devices / Android Composite ADB Interface and it works with no problem.
I have tried uninstalling / reinstalling both Android SDK tools v 21.1 using SDK manager and HTC Sync. I have uninstalled / re-installed the Google USB driver.
Tried entering this in android_winusb.inf file at the end of the [Google.NTamd64] section.
;HTC Incredible S
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF0
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF0&REV_0100
with no luck.
Also HTC Sync doesn’t seem to recognize the device either. I am running Windows 7 64 bit.
Does anyone know of a fix?
Quills88 said:
I’ve got driver problem with my Incredible S. When I have the phone on normally and connect it with a USB cable it shows:
Android USB Devices / Android Composite ADB Interface
in device manager. However, when I go into fastboot USB mode it just shows
Android USB Devices / My HTC
and it won’t recognize the device with Android SDK tools.
I can run fastboot commands using the cmd prompt but when I run ADB commands I get device not found or similar messages.
I have a HTC One S phone and in fastboot mode it shows correctly
Android USB Devices / Android Composite ADB Interface and it works with no problem.
I have tried uninstalling / reinstalling both Android SDK tools v 21.1 using SDK manager and HTC Sync. I have uninstalled / re-installed the Google USB driver.
Tried entering this in android_winusb.inf file at the end of the [Google.NTamd64] section.
;HTC Incredible S
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF0
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0FF0&REV_0100
with no luck.
Also HTC Sync doesn’t seem to recognize the device either. I am running Windows 7 64 bit.
Does anyone know of a fix?
Click to expand...
Click to collapse
Try installing the latest version of HTC Sync. It will install the most up to date drivers which are compatible with Windows 7 X64
Drivers
I've done that a few times. Perhaps because I have an AMD 64 bit the drivers don't work. It does seem like it a driver problem.

solved - adb device not recognized

I I apologize if this has been answered somewhere else. I did a couple of searches without finding an answer.
I can not get my MotoX to be a recognized device via adb. I am running Windows8 and I'm trying to get adb access to my ATT MotoX (DAMN, I wish I had a dev verstion!).
- It shows up under "other devices" as XT1058.
- It will not show up as an adb device in win8 device manager.
- I have tried different usb cables with the same result (and, different usb ports)
- I have changed the settings on Win8 to allow unsigned drivers.
- I have installed Moto Device Manager - didn't help.
- I have installed the Universal Naked drivers and "latest_usb_drivers_windows"
- I have uninstalled the device in device manager and de-selected/selected usb de-bugging and still comes up under "other devices"
- I have entered the Windows/Inf folder and deleted several inf files in an attempt to remove references to other drivers to get win8 to access the correct ones... hasn't worked so far....
Can someone please assist me in getting this thing recognized via adb?
I know fastboot is a separate issue - but, I can access fastboot so I'm fairly certain it is not a hardware issue (cable/port/etc).
------------------------------------------
Ok, I entered the folder Windows/Inf and opened up every single "oemN" file (N being the number following "oem") and deleted every file which had Android drivers... I then re-installed the Moto drivers and it worked...
Now, it says the device is "offline" - I need to research how to change THAT!
--------------------------------------
Ok, solved the "offline" issue... Updated the adb in "platform-tools" manually to 1.0.31
This caused the MotoX to FINALLY provide the pop up window to verify access to my computer's identity (which it refused to do previously).
Used this file: http://forum.xda-developers.com/attachment.php?attachmentid=1724500&d=1360704125
and copy/pasted the zip contents into the "platform-tools" folder to update the adb files.

[SOLVED] Please Help! Can't get fastboot to recognize device, but adb does

Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?
Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse
mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!

[Q] cant connect to pc in linux or windows

hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Nobody knows why? I have oem unlock "on"
debugging "on"
But I cant get my comp to see the device..Have Samsung drivers installed. Still no luck.
How can I fix this? all it does is charge when I hook it to pc but can't transfer files.
sorry double post
Same issue here. I've had no luck sorting it out.
Gutterball said:
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Click to expand...
Click to collapse
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
What the USB configuration is set to is actually moot. When the device is plugged in to a PC the tablet will bring up a notification stating what mode the USB port is in and also provide the option to change that to MTP mode (Transfer files), provided the drivers are correctly installed and all is in working order. By changing USB configuration to MTP the tablet shows up immediately on the PC but you still have to switch to "Transfer file" mode before you can move files between devices. Either way the results are the same and it takes the same number of steps. I always leave my USB configuration in "System Default" and I have never had any issues.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Gutterball said:
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Click to expand...
Click to collapse
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
I
BillTheCat said:
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
Click to expand...
Click to collapse
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
ashyx said:
I
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
Click to expand...
Click to collapse
Well, I'll be dipped in $hit.
What's the probability that one guy could have three dodgy USB cables? Used one, wiggled it around and the PC recognized the device. Looks like I'm in for a quick trip to WallyWorld. Thanks!
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Gutterball said:
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Click to expand...
Click to collapse
Are you able to connect to the device in TWRP, either ADB or MTP?
ashyx said:
Are you able to connect to the device in TWRP, either ADB or MTP?
Click to expand...
Click to collapse
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Gutterball said:
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Click to expand...
Click to collapse
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
ashyx said:
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
Click to expand...
Click to collapse
screenshot is in the attachment.

Categories

Resources