Develop Bugs

Device not recognized

I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...

It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.

mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..

Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.

This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.

chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot

Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.

chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?

bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?

chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).

mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?

chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.

@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.

bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.

I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader

brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*

Make sure USB debugging is turned on.
Sent from my Galaxy Nexus

mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*

Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?

mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus

[Q] adb/fastboot can't find device in bootloader, but they can do it when booted

Dear all,
I have worked on building Android from source code for few weeks. It used to be fine to me with my galaxy nexus, I can connect to my device via adb and fastboot and flash either the factory ROM or ROM built by me into my device. However, when updating the phone into 4.3, I forgot to extract drivers into the built directory and flash the built image into my device. Is surely can't work, and the screen turn off once "Google" is shown, so I would like to reflash it back to other image. However, my laptop can't recognize my Nexus S anymore in the bootloader. I can use "adb shell" once the device is normally booted (even without screen), but once I type "adb reboot bootloader", the connection is lost! Both "adb and fastboot devices" show nothing....
I have searched the forum and stackoverflow all day but can't find helpful information. There are many threads talking about unable to connect devices but 70% of them are driver-related issue and 30% of them, ex: sudo adb, just don't work for me. I think I am not facing the driver issue because I still can use "adb shell" once the device is normally booted (not in bootloader mode). Moreover, I also tried few debrick tools contributed by xda community but with no luck.
I am wondering if there is any way that I can reflash image to my device without accessing it in bootloader mode? (ex: push image in to device via adb shell when device is normally booted?). I am also wondering if there is any way to fix this problem. Any suggestion is very appreciated!: crying:
Thanks
Yu-Chih
ps. the most closed thread I found is called "ADB can discover devices but not fastboot" in stackexchange (I am not allowed to post the link)
but it seems there is no answer in this thread

I'm not a expert, but do you know how is the DD command ?,
I wonder, is you can DD the boot loader into the nexus partition?

chongns said:
I'm not a expert, but do you know how is the DD command ?,
I wonder, is you can DD the boot loader into the nexus partition?
Click to expand...
Click to collapse
Thanks for the reply. I am not sure what I should do with dd command? Could I use it to reinstall the drivers into device?
by the way, I found there is a error showing up in the bottom of screen in fastboot mode, "Fastboot Command Read Error -2147483647", and many closed threads (sorry that I am not allowed to post url because I am new). Some suggests are to reinstall drivers (even thought I don't get if they mean reinstall the usb driver for laptop or for android), but it seems not solved yet.
Yu-Chih

Dear all, I think I have tried all potential solution about "fastboot command read error -2147483647" that I can find at internet......
Here is what solution I have tried:
1. sudo the command of adb and fastboot
2. update drivers
3. update sdk
4. use another cable
5. install other drivers (win7), ex: naked driver
6. Wug's root kit
What I can't try:
1. enable USB debug mode at phone (because I don't have screen of it but only adb shell)
2. remove(uninstall) other software such as PDA net...etc (I don't try this because my system is clean-installed win7/MAC/ubuntu)
I think this problem is kind of common but my situation seems slightly different from others, that I can find the device when my device is normally booted but I can't recognize it when it is rebooted into bootloader (showing "fastboot command read error -2147483647" at bottom). I am starting to believe it either be the problem that I don't activate the USB debugging in my new flashed image (but I can connect it with adb when the device is normalled booted) or the usb driver in my device is broken.
Anyone has any idea.....:crying:
eddyxdxda said:
Thanks for the reply. I am not sure what I should do with dd command? Could I use it to reinstall the drivers into device?
by the way, I found there is a error showing up in the bottom of screen in fastboot mode, "Fastboot Command Read Error -2147483647", and many closed threads (sorry that I am not allowed to post url because I am new). Some suggests are to reinstall drivers (even thought I don't get if they mean reinstall the usb driver for laptop or for android), but it seems not solved yet.
Yu-Chih
Click to expand...
Click to collapse

Dear all,
This is my latest update. I wipe out the whole system of Ubuntu and Win7 and restart everything from the first step. Magically, the new Win7 + Wug's root kit can successfully flash new image into my phone. But also magically, the ubuntu system faces the same issue as I described (no connection in bootloader with the error code but connection is fine after the device is booted). The bright side of this is that I am finally able to try other solutions, e.g., enabling debugging mode, but the sad part is that I still get no luck at Ubuntu and MAC.........can't believe it works at Win7 but not at Ubuntu and MAC.....
Yu-Chih
eddyxdxda said:
Dear all, I think I have tried all potential solution about "fastboot command read error -2147483647" that I can find at internet......
Here is what solution I have tried:
1. sudo the command of adb and fastboot
2. update drivers
3. update sdk
4. use another cable
5. install other drivers (win7), ex: naked driver
6. Wug's root kit
What I can't try:
1. enable USB debug mode at phone (because I don't have screen of it but only adb shell)
2. remove(uninstall) other software such as PDA net...etc (I don't try this because my system is clean-installed win7/MAC/ubuntu)
I think this problem is kind of common but my situation seems slightly different from others, that I can find the device when my device is normally booted but I can't recognize it when it is rebooted into bootloader (showing "fastboot command read error -2147483647" at bottom). I am starting to believe it either be the problem that I don't activate the USB debugging in my new flashed image (but I can connect it with adb when the device is normalled booted) or the usb driver in my device is broken.
Anyone has any idea.....:crying:
Click to expand...
Click to collapse

(help please) htc one m8 not showing in adb command prompt while in fastboot.

so I'm trying to fastboot flash TWRP. That way I can root it after the custom recovery is set up.
My HTC is S-OFF, I installed android studio for the adb fastboot command prompt. Then installed all HTC drivers. I then plugged in my HTC into my pc which is running windows 10 via USB port which are 3.0
I opened up the folder where the fastboot was installed when I downloaded android studio. Then I pushed shift and right clicked and chose open command promp. I then typed: adb devices
The command prompt runs and it shows my HTC in the device list. Then I typed: adb reboot bootloader. It boots to the fastboot.
And so here is my problem........... once I boots to fastboot I thenjoy again type: adb devices. Cmd runs and the device list is blank. I checked my drivers and device in device manager and everything is fine. Even I'm fastboot it reads the drivers no problem.
I've tried everything. I've read to try reinstalling the drivers, try installing universal drivers, try different USB cables, try different USB ports that arent 3.0 port, I even tried a different adb fastboot software and still came up with the same outcome. I've read a bunch of different threads and just can't find anything. I am just stuck I don't know what to do. And am asking for help please. I would really appreciate the help and guidance. Because....... this s**t is driving me crazy haha. I've rooted galaxies and have my s5 on lollipop rooted. But
I'm still a noob and especially with HTC. So please some one lend me a helping head I am at a complete loss.

Whisperz6662 said:
so I'm trying to fastboot flash TWRP. That way I can root it after the custom recovery is set up.
My HTC is S-OFF, I installed android studio for the adb fastboot command prompt. Then installed all HTC drivers. I then plugged in my HTC into my pc which is running windows 10 via USB port which are 3.0
I opened up the folder where the fastboot was installed when I downloaded android studio. Then I pushed shift and right clicked and chose open command promp. I then typed: adb devices
The command prompt runs and it shows my HTC in the device list. Then I typed: adb reboot bootloader. It boots to the fastboot.
And so here is my problem........... once I boots to fastboot I thenjoy again type: adb devices. Cmd runs and the device list is blank. I checked my drivers and device in device manager and everything is fine. Even I'm fastboot it reads the drivers no problem.
I've tried everything. I've read to try reinstalling the drivers, try installing universal drivers, try different USB cables, try different USB ports that arent 3.0 port, I even tried a different adb fastboot software and still came up with the same outcome. I've read a bunch of different threads and just can't find anything. I am just stuck I don't know what to do. And am asking for help please. I would really appreciate the help and guidance. Because....... this s**t is driving me crazy haha. I've rooted galaxies and have my s5 on lollipop rooted. But
I'm still a noob and especially with HTC. So please some one lend me a helping head I am at a complete loss.
Click to expand...
Click to collapse
You're using the wrong command.
You can't use adb commands when booted to bootloader, only while booted to system, as you did the first time.
Once you do adb reboot bootloader use fastboot devices and your phone will show in cmd. You need to use fastboot commands while booted to bootloader.

xunholyx said:
You're using the wrong command.
You can't use adb commands when booted to bootloader, only while booted to system, as you did the first time.
Once you do adb reboot bootloader use fastboot devices and your phone will show in cmd. You need to use fastboot commands while booted to bootloader.
Click to expand...
Click to collapse
Wow that was so simple...... (face palm)
You are a saint haha. Thank you very much that was getting to me. It did show up was able to flash twrp.
No where did I see anything about typing fastboot in cmd instead of adb while phone was in fastboot. Well it might of and I might of just not of understood it when I read it. Again thank you I appreciate it

Fastboot interface is missing. Help!

On Device Manager (Window 10). Were updating the driver, I can only see ADB interface but no Fastboot interface. I'm on the latest version SDK from Google and have OnePlus driver installed. I can command ADB but not fastboot. What am I missing? My device is OnePlus 7T TMobile is sim unlocked and I can toggle OEM unlocking and is on.

Not sure what mean, but fastboot only works when you're booted in bootloader. (Adb reboot bootloader)
Sent from my OnePlus7TPro using XDA Labs

That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.

PesTicide. said:
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
Click to expand...
Click to collapse
I myself have never had this problem, I can only suggestion reinstalling OnePlus drivers.
Hopefully you figure this out
Sent from my OnePlus7TPro using XDA Labs

I reinstalled couple of times. Still no go! This is the first time that this happening. Never had problem since day one on Nexus devices. I'm going to try again and search more around.

You can also use the universal drivers by clockworkmod https://adb.clockworkmod.com/
Here's what I did.
1) Extract the android sdk platform tools and put on your c:// drive
2) Install the universal usb drivers
3) Enable usb debugging on your one plus and connect to computer. Switch to usb debugging mode and accept the popup on your one plus to allow the connection.
4) Open cmd and run "cd C:\platform-tools", then run "adb devices" to ensure that your devices is connected properly
5) Run "reboot bootloader" and device will restart into bootloader mode and fastboot will now work
*This is all assuming that you've already oem unlocked your devices as well already*

It work till fastboot. Still stuck at "waiting for device".

PesTicide. said:
It work till fastboot. Still stuck at "waiting for device".
Click to expand...
Click to collapse
Are you trying to open? Command shell? In windows 10 right? So for your information in windows 10 it's not supported , you have to open that platform tool folder which you installed already named as adb, platform tools , sdk may go into that folder and you will see a folders directory above there .. just click on that and type cmd and hit enter and cmd will pop up now you can use all your commands it's not your fault it's windows 10 fault ..maybe hope it may work for you

That how I done it. Fastboot Command appear on my Google Pixel 2 and 3 but I can't do it on my 7T. I don't get it
Thanks for the help! I tried working on Device Manager on PC yet doesn't work. Adb shell command work but no Fastboot command.

I found the solution! This is what I did and it worked for me! Here's the link for anyone who has the same issue I went through. Here you go and follow the instruction. http://www.wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Mod you can close this thread. Thanks again for everyone who tried to help me. :highfive:

ADB and fastboot cannot detect the phone

Hello, I have two unlocked Pixel 2XL, one works without a problem, it is detected by adb and fastboot. The second one during boot has bootloop. When I try to turn it into fastboot mode, the screen of this mode is shown, but after connecting the cable (which works on the first fully working phone) and entering the command "fastboot devices" nothing happens. In device manager I only have 'device not detected or working incorrectly (code 43 or sometimes code 10). When trying to enter TWRP, the phone completely stutters and displays only the TWRP start screen without any other symptoms. I have good drivers installed because the computer detects this working phone without a problem ... Do I have a damaged USB port on the phone? Is there another explanation and solution for this?

binarnh said:
Hello, I have two unlocked Pixel 2XL, one works without a problem, it is detected by adb and fastboot. The second one during boot has bootloop. When I try to turn it into fastboot mode, the screen of this mode is shown, but after connecting the cable (which works on the first fully working phone) and entering the command "fastboot devices" nothing happens. In device manager I only have 'device not detected or working incorrectly (code 43 or sometimes code 10). When trying to enter TWRP, the phone completely stutters and displays only the TWRP start screen without any other symptoms. I have good drivers installed because the computer detects this working phone without a problem ... Do I have a damaged USB port on the phone? Is there another explanation and solution for this?
Click to expand...
Click to collapse
Most likely the culprit is either out of date platform-tools or TWRP...
What version of adb, fastboot, & TWRP are you using? Also, how are you booting TWRP -- there have been many cases where people would use the command "fastboot flash boot twrp.img" instead of booting temporarily...
Hope this ends up being helpful as that means it resolves it...

Are you able to fastboot boot the latest twrp.img?
Might want to give Deuces script a whirl. I've seen this fix situations like yours.

ADB version: 1.0.41 29.0.5-5949299, TWRP: twrp-pixel2-installer-taimen-3.3.0-0 Latest Rom istalled on this phone is Havoc OS 2.8 for P2XL. I trying to enter TWRP via fastboot and choose recovery there, but stuck on TWRP logo... When I try to enter a command: "fastboot boot twrp.img" receives a message: <waiting for any device>
edit: Deuces script log says: "Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version 29.0.5-5949299
Installed as C:\Users\marek\Desktop\platform-tools\fastboot.exe
Fastboot Detected!
Checking if device is detected via Fastboot.
Error: Device not detected via Fastboot.
Check device cables and fastboot drivers..."
But cable and drivers is good because other pixel 2xl works fine with it...

binarnh said:
ADB version: 1.0.41 29.0.5-5949299, TWRP: twrp-pixel2-installer-taimen-3.3.0-0 Latest Rom istalled on this phone is Havoc OS 2.8 for P2XL. I trying to enter TWRP via fastboot and choose recovery there, but stuck on TWRP logo... When I try to enter a command: "fastboot boot twrp.img" receives a message: <waiting for any device>
edit: Deuces script log says: "Welcome to Deuces Flashing Script!
v5.0-Windows
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
fastboot version 29.0.5-5949299
Installed as C:\Users\marek\Desktop\platform-tools\fastboot.exe
Fastboot Detected!
Checking if device is detected via Fastboot.
Error: Device not detected via Fastboot.
Check device cables and fastboot drivers..."
But cable and drivers is good because other pixel 2xl works fine with it...
Click to expand...
Click to collapse
This might sound crazy, but, at least try another USB A to C cable, and other ports on your pc. The P2XL is notorious for being finicky when it comes to cables and ports. What might work for one phone, doesn't necessarily mean it will for the other. Make sure it's a 2.0 USB cable as well :good:

I checked four different cables and all ports on my computer and still not lucky... I even checked on another computer and still the same

binarnh said:
I checked four different cables and all ports on my computer and still not lucky... I even checked on another computer and still the same
Click to expand...
Click to collapse
Then it's likely a hardware/port issue would be my guess.

Meh, so I will look for a workshop nearby that will exchange the port for me and check later

I would also suggest that you re-download EVERYTHING...
You may be stuck with a "buggy" TWRP image file or platform tools....and/or go against conventional thinking and download and try an older version of TWRP to see if it does it at that point as well...
In either case, hopefully you get it figured out and good luck to you...hope this ends up being helpful!

There were a number of Pixel 2 XL's that did suffer from charging port issues, including my original. Luckily I was still under warranty and was issued a replacement. The phones would charge fine but data did not transfer as with adb/fastboot, nor would Android Auto work.
https://forum.xda-developers.com/pixel-2-xl/help/pixel-2-xl-charging-port-damaged-t3783638

Update: fastboot and adb detect device but when I try flash factory image fastboot says: "fastboot: error: cannot determine image filename for"

binarnh said:
Update: fastboot and adb detect device but when I try flash factory image fastboot says: "fastboot: error: cannot determine image filename for"
Click to expand...
Click to collapse
What fastboot command did you give?

Badger50 said:
What fastboot command did you give?
Click to expand...
Click to collapse
I use flash all script

binarnh said:
I use flash all script
Click to expand...
Click to collapse
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?

Badger50 said:
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Click to expand...
Click to collapse
Yes for all your questions. I try 3 different cables

binarnh said:
Yes for all your questions. I try 3 different cables
Click to expand...
Click to collapse
Not running platform-tools through power shell either are you?
What happens when you try double clicking on the flash-all.bat file with your mouse?

binarnh said:
Badger50 said:
Platform-tools are up to date?
Did you open your command prompt directly on the platform-tools folder?
When you typed in "fastboot devices" did you see your device ID Number?
Are you using a 2.0 USB A to USB C cable?
Click to expand...
Click to collapse
Yes for all your questions. I try 3 different cables
Click to expand...
Click to collapse
Based on your error, I'm guessing all the files in the Full Factory .zip file (all 6 of them) aren’t residing there with the adb & fastboot .exe files within the platform-tools folder. Make sure you’re seeing those 6 files (you will have a two .sh files, two .img files, one .zip file, etc.) with the .exe adb & fastboot file.
Then, also make sure that you are directing your powershell or command prompt to the correct “platform-tools” folder, because many other people seem to have multiple “platform-tools” folders and they end up directing to a wrong folder…
Hope this ends up being helpful…

I fixed it! The error in fastboot mode probably came from a file that I extracted from winrar, when I downloaded the factory image again and extracted the files this time through 7zip and copied them to the platform-tools folder and double-clicked flash-all.bat fastboot started and the installation was successful! Thanks to everyone who wanted to help me solve this problem <3
ps. btw, I haven't replaced this broken port on the phone... just started working again...