So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
First off, I barely know anything with regards to phones as I still learning. However, last night had a similar issue and ended up having to use cmd prompt to navigate to adb and then used it to see the device.
MrTechie890 said:
So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
Click to expand...
Click to collapse
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
BD619 said:
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
Click to expand...
Click to collapse
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
MrTechie890 said:
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
Click to expand...
Click to collapse
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
tdhite said:
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
Click to expand...
Click to collapse
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
MrTechie890 said:
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
Click to expand...
Click to collapse
Then try this:
adb backup
That should create a backup file called: backup.ab
tdhite said:
Then try this:
adb backup
That should create a backup file called: backup.ab
Click to expand...
Click to collapse
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
MrTechie890 said:
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
Click to expand...
Click to collapse
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
tdhite said:
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
Click to expand...
Click to collapse
For me, doing it on Linux wouldn't be a huge issue but since I have a mac as my primary machine I'm trying to make due with it.
I think I just firgured it out actually. I just had to install the android sdk, I was using the abd files provided from a tutorial. anyhow, thanks for trying to help tdhite.
Related
Once i got my new nook color i rooted it with auto nooter, and im running 1.0.1, on my previous nook i rooted it and adb worked right then, now i cant get adb access, im using the same computer and everything, all thats diferent is its a new nook. I have full root access and can install apps and everything. Any help?
Seems to be a common problem. You can launch NookColorTools and fix it temporarily. Go to "Development" and then unchecked and then recheck the USB Debugging box.
Ok I've been doing that for a while and finnaly got the message that USB debugging is only for development. It works now......
Sent from my LogicPD Zoom2 using XDA App
Get ADB wireless, it works great.
I've had zero luck using usb adb, but adb wireless works great!
I was having similar issues so after many many attempts I just decided to go with adb wireless and would definitely recommend going that route if you can't get it working over usb.
Yeah, getting ADB to work requires a lot of uninstalling/reinstalling drivers and unplugging/replugging the device, it's very temperamental.
can someone link me to a link on how to use/setup adb wireless
beezy69 said:
can someone link me to a link on how to use/setup adb wireless
Click to expand...
Click to collapse
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
chemical1der said:
https://market.android.com/details?id=siir.es.adbWireless
it's free in the market and once you download it set up is easy. i've used it through my mac terminal as well as through ubuntu. like the posters above i had the hardest time getting adb to work via usb.
Click to expand...
Click to collapse
is there any tutorials on how to use it and what commands i need to install apps?
beezy69 said:
is there any tutorials on how to use it and what commands i need to install apps?
Click to expand...
Click to collapse
once you've installed adb on your computer type "adb" at your terminal prompt and you should list of commands there.
here's the link to Android Developer's ADB website (this also lists commands):
http://developer.android.com/guide/developing/tools/adb.html
files and installation directions can be found here:
http://developer.android.com/sdk/index.html
Good luck!
Ok so me being my dumb self forgot to install the adb drivers for the nook....... im dumb haha, but i cant get them to install, every time i uninstall the mass storage driver so i can install the proper driver it automatically re-installs it....... HELPPPPPPP
Is there any way to download this to the SD and install it from there? I've upgraded to a version of froyo, which doesn't have the market, and my command line won't work after swapping nooks.
I can't seem to get mine to work with either adbwireless or via usb.
Using USB I get this:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android-sdk-windows\platform-tools>
Here is what I get if I try to connect using adbwireless:
C:\android-sdk-windows\platform-tools>adb connect 192.168.2.4:5555
already connected to 192.168.2.4:5555
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
192.168.2.4:5555 device
C:\android-sdk-windows\platform-tools>
But it doesn't show a serial number like all the HowTo's says it should. What am I missing?
EDIT: HALLELUJAH!!
I fixed it. Actually I didn't fix it, I just followed some instructions from another user that was having the same problem and finally figured out the very weird thing that installing the drivers did. Anyway, here is the solution from hacku:
Originally Posted by hacku View Post
Thanks for this...
EDIT 1:
I followed your instructions to a T and I still can't get ADB to see my NC. After uninstalling all instances of Nook in my device manager, unplugging it and plugging it back in, it adds all the same devices:
Under Disk Drives it lists B&N Ebook Disk USB Device (twice)
Under Portable Devices it lists MyNookColor
Under USB Controllers it lists USB Mass Storage Device
My PC is Windows 7 Ultimate 64bit. Running Nook Color 1.1.0 rooted and overclocked to 1.1Ghz. Any help will be greatly appreciated.
EDIT 2:
So I decided to pull the MicroSD card to simplify things. Uninstalled all instances of Nook from Device Manager and scanned for new hardware. This time I noticed that Windows detected it as a Nook, but then would install the drivers and it would show the same USB Mass Storage Device and the two instances of B&N Disk USB Device. I also noticed that by uninstalling the driver of the USB Mass Storage Device automatically deleted the other two instances under Disk Drives. So I updated the USB Mass Storage Device driver and this time I was able to install the drivers provided, but now it only shows up as an Android Phone > Android ADB Interface (not Composite), but I'm still not able to see it under adb devices.
Help?
EDIT 3:
GOT IT WORKING!!!
For those of you having this same problem this is what I did:
1. Right Click Android ADB Interface (it won't say Composite)
2. Select Update Update Driver Software
3. Click on Browse My Computer For Driver Software
4. Click on Let me pick from a list of device drivers on my computer
5. In the box that pops up click on USB Composite Device
6. Click Next
It now installed the USB Composite Device driver and changes your Android Phone to Android Composite ADB Device.
Open up Command Prompt and type adb kill-server then adb devices and your Nook Color will now show up.
Hope this helps some of you out.
This thing really needs to be pinned somewhere, preferably with IOMonster's first post. There's so many of us starting on this from scratch not able to get adb to see the device. har02's crosspost of hacku's post is what finally got it to work for me. there's a ton of junk out there that just doesn't make sense, and the installing the second driver on the "android interface" is a step that is completely missing from just about every post on this topic.
Aside from that, this forum is what got me buying a nook and happily learning all sorts of cool new things!
THANK you so much har02052, this marks the end of a 6 hour nook-fixing marathong....ahhhhh
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
nikpmr said:
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
Click to expand...
Click to collapse
Does it show up when typing adb devices in the command prompt?
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
nikpmr said:
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
Click to expand...
Click to collapse
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Try to force ADB to redetect with adb kill-server.
abrahammmmmmm_ said:
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Click to expand...
Click to collapse
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
nikpmr said:
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
Click to expand...
Click to collapse
Is your computer windows 7, 8 x32 or x64bit? I can probably do it today if you've got a windows 7 x64bit computer since I wont have to do much looking
I'm running win 7 64 bit. Thanks again for your help!
nikpmr said:
I'm running win 7 64 bit. Thanks again for your help!
Click to expand...
Click to collapse
NOTE THAT YOUR PHONE SHOULD NOT BE CONNECTED DURING THIS PROCESS
I already searched & set up the update folder so you don't have to do all the dirty work d:\
Ok Well I'm just going to make this quick and not really got through the basics like how to unzip things because if you don't know how to do that you probably shouldn't be trying to get s-off on your phone anyway so I'll just assume you already know how.
Step 1. open control panel select hardware and sound and open Device Manager with the administrative logo one the side.
Step 2. Near the top or somewhere on this list there's supposed to be a drop down that reads "adb devices, adb android, adb, android, adb drivers etc. Mine shows Android USB Devices it actually just varies based on computer I can't really go to the specifics of it but I'm sure you can find it.
Step 3. Select that dropdown menu and right click whatever shows (there should only be one thing) and then select Update Driver Software and choose the option that says Browse my computer for driver software and locate the htc drivers folder which should already be unzipped, select the whole folder and have the option to include subfolders checked. click next or whatever it says to finish
Step 3 Now you must remove your device from the Portable Devices dropdown menu to ensure all drivers are detected for the phone, to do this right click on HTC First and just select remove, wait until it's done. and now just reconnect your device and let all the drivers install and it should now be done!
Make sure you look at the screenshots I attached to make sure you don't accidentally remove or update something else also because that's where the drivers folder is an i'm pretty sure you'll need that
A reboot of the computer is recommended btw
Ask questions if you have any
View attachment 2459140
View attachment HTC_drivers_Win7_x64.zip
View attachment 2459141
Wow, that's quite explanatory, thank you! Unfortunately I only see the category ADB Devices when the phone is connected and in recovery mode, and I only see the category Portable Devices when the phone is connected, booted, and in debug mode. (Neither of these categories are visible when the phone is disconnected from the computer.) I did however try installing the drivers you gave me with the phone connected and in recovery mode, but to no avail; after the phone boots ADB Devices disappears and Portable Devices appears. Uninstalling Portable Devices doesn't help either; it just reinstalls when I reconnect the phone.
I am trying to get the category ADB Devices to appear in the Device manager when the phone is turned on and in debug mode so that I can use ADB while the phone is booted.
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
nikpmr said:
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
Click to expand...
Click to collapse
How exactly did you replace the HTC First driver with the Generic USB Composite Device Driver?
the device is not found however I installed the drivers and I am using windows 7 I tried it with another computer and it didn't work
and it works with the recovery I want it to work to gain s-off
RedBlackPellet said:
the device is not found however I installed the drivers and I am using windows 7 I tried it with another computer and it didn't work
and it works with the recovery I want it to work to gain s-off
Click to expand...
Click to collapse
check FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
nkk71 said:
check FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
I tried with different devices laptops and mobiles and I always get device not found and different adb sdks
RedBlackPellet said:
I tried with different devices laptops and mobiles and I always get device not found and different adb sdks
Click to expand...
Click to collapse
if your booted into a rom, do you have usb debugging enabled ?
its in system, developer options, if you cant see developer options then goto about - software information - more - and tap build number 7 times, it will count down and eventually say you are now a developer, you should now see developer options in your system menu.
when you enable usb debugging and plug your phone into the computer.....eventually.....and sometimes it takes a while, you will get a pop up on your phone saying your computer wants to connect to this device, allow or deny, I suggest you allow.
if you don't get the message, then with the phone still plugged into the computer, open developer options again and disable usb debugging, then enable it again.
Seanie280672 said:
if your booted into a rom, do you have usb debugging enabled ?
its in system, developer options, if you cant see developer options then goto about - software information - more - and tap build number 7 times, it will count down and eventually say you are now a developer, you should now see developer options in your system menu.
when you enable usb debugging and plug your phone into the computer.....eventually.....and sometimes it takes a while, you will get a pop up on your phone saying your computer wants to connect to this device, allow or deny, I suggest you allow.
if you don't get the message, then with the phone still plugged into the computer, open developer options again and disable usb debugging, then enable it again.
Click to expand...
Click to collapse
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
RedBlackPellet said:
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
Click to expand...
Click to collapse
im at a loss, sorry I couldn't help any further, but if its doing it with different devices, it has to be a software issue, especially as you say its working in recovery and bootloader, the only thingf I picked out from your picture is it states your adb is out of date, but you say you've tried that too, all I can suggest is you try this one.
http://forum.xda-developers.com/showthread.php?t=2588979
also where did you get the drivers from
RedBlackPellet said:
and sometimes device offline
Click to expand...
Click to collapse
reboot PC and phone, use a USB2 port
RedBlackPellet said:
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
Click to expand...
Click to collapse
why are you using an adb shell to push the file? push the file using adb and then enter the shell to chmod the "ff" file (I suppose you are pushing firewater but your renamed the file to "ff" ?) And btw "adb devices" will not output your device ID from an adb shell.
Code:
adb devices
adb push ff /data/local/tmp
then
Code:
adb shell
su ---> [COLOR="blue"]to get a # prompt[/COLOR]
chmod 775 /data/local/tmp/ff [COLOR="Blue"]--> to give read/write/execute permission[/COLOR]
/data/local/tmp/ff
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Cheetohz said:
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Click to expand...
Click to collapse
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
PaisanNYC said:
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
Click to expand...
Click to collapse
I actually did nto check device manager. but I had the safely eject Nexus 6 show up in my task bar, so it was recognizing it as a nexus.
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.