Im losing my mind. - Samsung Galaxy Gear

I must be missing something and its driving me crazy.
I am trying to install Null_ to my gear, I was able to follow the guide and use odin to install TWRP on the gear, that was easy. Now I'm losing my hair trying to send the null_23 zip to the gear.
I've tried sending via NFC, no luck.
Tried sending via bluetooth, no luck.
I tried ADP Push null_23.zip /sdcard but my gear doesn't appear to have ADB installed.
I can't install ADB without root.
Can't install root without internet
Can't get internet without bluetooth tethering
Can't seem to enable bluetooth tethering without root?
I am losing my mind!
Every guide I find says "transfer the file to the gear and install with TWRP" but they forget that some of us are new to the galaxy gear and might not know how to do that!
If someone could please give me some sanity and explain how I can transfer these files to get it working I would appreciate it very much because every guide i've seen to date seems to think i know what im doing (protip, I don't, thats why im reading the guide)

Did you enable usb debugging on the gear?

440bro said:
Did you enable usb debugging on the gear?
Click to expand...
Click to collapse
Yes.
Finally got it working (Kind of), turns out my computer didnt have proper drivers installed, had to go to the device manager and manually uninstall the drivers, then reinstall the samsung ones, then change the USB port I was connected to so the computer checked for drivers and installed it properly. After all that it detected the watch but STILL wouldnt let me ADB.
I FINALLY was able to ADB the files over by using the "Universal ADB Driver" package. http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
Hopefully anyone else having these issues can find this information useful. Its not always a device issue but could be the computer doesnt have the right drivers.
Thanks!

Related

SOLVED: adb help for "error: device not found" after reboot from cmd

sorry if this clutters up the forum for a bit, i promise to delete it when it dies.
i've recently started using adb when i flashed over to 5.0.2h. i followed the instructions in the tutorial and was able to use adb. 2 nights ago, i began doing more complicated commands (for me) and tried to push a .apk into /system/app.
i wasn't immediately successful but i eventually got it in there and decided to reboot my phone. after this reboot, however, i lost the use of adb. i tried upgrading to the usb drivers haykuro posted, uninstalling them and re-trying the old one, rebooting the computer, rebooting my phone and none of it works. i've since wiped my phone and flashed it with the latest h build from haykuro (thanks haykuro!) but that didn't work either. now i'm trying to see if the 1.5 sdk will work.
i was wondering if anyone would have an idea about what i should do next. should i reinstall adb? try it on another computer? another cable? it's not the worst loss in the world, my phone is fine and my usb cable still works in the conventional way. i even checked to see if i somehow lost root and i was able to get su on the terminal emulator. but i still want the use of adb for nandroid, if nothing else.
thanks in advance!
I had the same problem after flashing to the G rom. I couldn't get ADB to work but fastboot recognized my phone and I was able to flash back to my backup. First time I did a complete wipe before flashing, second time, no wipe, made no difference in either case for me
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
I just had the same problem, I had to update the driver and it is working fine now.
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
zer0day said:
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
Click to expand...
Click to collapse
Give me a few minutes I will find you a link for it.
jordanjf86 said:
Give me a few minutes I will find you a link for it.
Click to expand...
Click to collapse
Here it is. http://dl.google.com/android/android_usb_windows.zip after downloading this when you go to update your driver in device manager make sure to use this. Hopefully this will help it worked for me.
jashsu said:
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
Click to expand...
Click to collapse
yes, that's what it comes up as. and i've tried the usb drivers from haykuro's page and they didn't work before and after rebooting my computer.
i'm on vista and it wont accept the updated drivers. it downloads the standard removable memory drivers and wont let me update to anything else. anybody have any ideas
just installed the 1.5 apk and adb and it works again. for people running haykuro builds, i would suggest trying this if you have adb problems. just intall the 1.5 sdk as normal, copy adb.exe and AdbWinApi.dll into \system32 and you should be good.
unless requested i will delete this thread in two days. thanks everyone!
Hmm... i tried that and its still not working ):
Ive tried like 10 different USB drivers from various sites including this one, downloaded the 1.5 SDK and installed it, wen through several reboots and it always says either that the driver is for the wrong platform, the most up to date one is ALREADY installed (HTC Bootloader), or that Windows couldn't find any drivers.
Under ADB Interface in device manager is "%USB\VID_0BB4&PID0FFF.DeviceDescRelease%"
did you try and update the driver through the device manager? i've heard that it's the only way to update it for some people.
I had already Posted & Solved This Issue here : http://forum.xda-developers.com/showthread.php?t=493703
Go Check It, It ll work for sure....
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Hi
I actually replying about the bible quote you have mentioned? you into theology?

Driver Help

Note: I have searched the forums/google/youtube and done just about everything suggested.
I downloaded the SDK thinking my computer would notice the drivers ... it doesn't
I've installed, uninstalled, rebooted, power cycled, disonnected, reconnected, deleted, added etc... And Windows still does not recognize my Hero.
I don't know what to do now, as I thought I was going to just simply root and keep it moving, but I can't even get transfer contacts yet. Anybody have suggestions? Tips? Anything? I'm desperate here
Running: Vista x64
Make sure you download and install HTC Sync here and turn on USB Debugging on your phone by pressing menu, settings, applications, development, and check USB debugging. Also turn on unknown sources in the same menu in applications.
Dave2582 said:
Make sure you download and install HTC Sync here and turn on USB Debugging on your phone by pressing menu, settings, applications, development, and check USB debugging. Also turn on unknown sources in the same menu in applications.
Click to expand...
Click to collapse
I've done this too ... multiple times
Ok, try this link and download the htc drivers for the hero. When its looking for the drivers, browse for the location yourself and point it to the drivers that you downloaded (once you extracted it)
Dave2582 said:
Ok, try this link and download the htc drivers for the hero. When its looking for the drivers, browse for the location yourself and point it to the drivers that you downloaded (once you extracted it)
Click to expand...
Click to collapse
Sigh, tried this too. Windows just keeps telling me it cant find the driver - even when I direct it to the folder I've never had this happen with any other drivers I've installed
try removing the device in device manager and remove SDK and then go back through the steps of installing htc sync plug in your phone then run SDK
Kenpoman said:
try removing the device in device manager and remove SDK and then go back through the steps of installing htc sync plug in your phone then run SDK
Click to expand...
Click to collapse
Lol yea I've done that too. Maybe it's my system. I just plugged the damn thing in to my office computer and the phone recognized the USB, and on the computer I can see the mSD - none of which have happened on my system at home.
Thanks for all the help, if anybody else has suggestions feel free to keep em comin!
i have had problems with two of the four computers that I have it installed on.
both of them i think i used different versions of SYNC to get it to work but I can't remember.
Kenpoman said:
i have had problems with two of the four computers that I have it installed on.
both of them i think i used different versions of SYNC to get it to work but I can't remember.
Click to expand...
Click to collapse
I'd be happy to even get THAT far. My computer wont install drivers, my phone doesn't detect that its connected via usb, so I'm unable to mount. So there's no chance of even using SYNC yet lol. I guess I should be happy I didn't rush out to get that EVO just yet, cuz I'd kill over if I were having this problem with that phone. With the Hero, it's annoying cuz I can't transfer music or root yet.
The following accurately sums my emotional roller coaster the last 24hrs ...
... ... ... ... ... ...
I had a similar problem. First does you phone charge from the USB port? if not find a different USB cable. I have heard thicker is better but all the ones I have tried have charged it.
If it does charge but you can get Windows to recognize it as ADB then install PDAnet on your computer. You can find it with a google search. I got really frusturaded getting the drivers to work too, but PDAnet worked on the first try.
Fazulka said:
I had a similar problem. First does you phone charge from the USB port? if not find a different USB cable. I have heard thicker is better but all the ones I have tried have charged it.
If it does charge but you can get Windows to recognize it as ADB then install PDAnet on your computer. You can find it with a google search. I got really frusturaded getting the drivers to work too, but PDAnet worked on the first try.
Click to expand...
Click to collapse
I use the stock USB, which does charge it via any USB connection. However I notice that when I plug it into a system at work (Windows 7) the phone recognizes the USB connection and allows me to mount [I'm adding music I sent to myself this morning to the phone via this Win7 system]. Whereas the system at home the phone doesn't even see a USB connection present, so no mounting option. (I've tried all 4 USB ports on my personal laptop)
I'll DL PDAnet either tonight or tomorrow and see how this works. Thanks for the suggestion, and I'll keep you posted.
--off to find this XDA android app--
amorphouskev said:
I use the stock USB, which does charge it via any USB connection. However I notice that when I plug it into a system at work (Windows 7) the phone recognizes the USB connection and allows me to mount [I'm adding music I sent to myself this morning to the phone via this Win7 system]. Whereas the system at home the phone doesn't even see a USB connection present, so no mounting option. (I've tried all 4 USB ports on my personal laptop)
I'll DL PDAnet either tonight or tomorrow and see how this works. Thanks for the suggestion, and I'll keep you posted.
--off to find this XDA android app--
Click to expand...
Click to collapse
Pdanet is the only way my computer would recognize it also so that should work for u.
Papa Smurf151 said:
Pdanet is the only way my computer would recognize it also so that should work for u.
Click to expand...
Click to collapse
Didnt work. I kinda give up.
My phone only gives me the mount USB option when my PC is booting. As soon as I log in to windows that option goes away.
Sent from my HERO200 using XDA App
seriously try a to install a different version of sync first. i am using two different versions .
Kenpoman said:
seriously try a to install a different version of sync first. i am using two different versions .
Click to expand...
Click to collapse
Ok I've finally gotten the phone and computer to see each other. So I now have access to the SD card, however Vista still is not locating drivers.
Methods tried:
Installing, Uninstalling HTC Sync (various versions, new & old - including several reboots)
A tether program suggested in this thread
PDAnet
Directed Vista to folders with drivers.
Downloaded suggested drivers to Vista and pointed the system to particular folder
It's great that now I can take care of adding music etc... to the phone, but I had hopes of rooting as well, and it doesn't look like that's going to be a reality.
I'm still completely open to suggestions, and very grateful for all the assistance so far!
Since I just got this phone from asurion it's still on 1.5 would updating help? (I didn't want to update android for fear that I wouldn't be able to root, as I heard some update went out that prevented ppl from rooting)
-----------------
UPDATE:
I must have THE WORST Karma in the world, as soon as I posted this I stopped being able to see my SD card, and the phone keeps wanting to sync with HTC sync. No option to mount the USB anymore. I'm ready to bash my head and this phone repeatedly into a brick wall (after throwing my notebook off a balcony)
do you have sdk installed.
i had a hell of a time and ended up installing sdk in mydocuments instead of the root C:
again this is just one computer. my windows 7 machine was good from the start.
i haven't tried vista yet.
let me retrace my steps and see if i can help
this is also an option for rooting http://unrevoked.com/
i haven't tried it myself but you can download it to your phone and with a file explorer you can install it.
I've given up. This issue has made just pushed me completely away from Windows. I've realized that practically any USB device plugged in (except my old win mobile device) isn't recognized. Switching to Linux and hopefully a more compatible android experience.
Thanks for all the help!
Sent from my HERO200 using XDA App
My only thought (after having similar problems at work) is that there are still driver issues. I found a program called USBDeview that can be used to remove drivers left behind by other removal methods. It requires admin rights, so if you don't have those, sorry. If you still want to try, the program was a free download found using Google. Remove the drivers, reboot, and give it one more try.

[Q]

Well, my problem is that my phone won't recognize any computer as a computer, but only as a source for battery charging. when i plug it into a computer the battery starts charging but i don't get the USB sign.
the thing is that it used to work. i usually just pluged the phone in and it would work, and suddenly out of the blue it stopped working and i have no idea why. i've done nothing on the computer between the last time it worked and the time it stopped working, i wasn't even using the computer during that time, so it must be something on the phone settings, but i checked it a little and found nothing that looks like the problem, but i rly don't understand much about it..
any ideas?
It sounds like a driver issue.
If you're using a Samsung firmware, reinstall the drivers. This can be done by finding them online, or by installing Kies. If you're using CM7/Miui, Samsung drivers won't work. You'll need to uninstall Kies (or kill the process to make sure it's not running in Task Manager) and then install the Nexus S drivers. Again, a simple search will provide the files you need.
If it's not a driver issue, I really don't know what it could be. But I would definitely try reinstalling the appropriate drivers first.
Go to Settings>Applications>Development and if USB debbugging is flagged,deflag it!
upichie said:
It sounds like a driver issue.
If you're using a Samsung firmware, reinstall the drivers. This can be done by finding them online, or by installing Kies. If you're using CM7/Miui, Samsung drivers won't work. You'll need to uninstall Kies (or kill the process to make sure it's not running in Task Manager) and then install the Nexus S drivers. Again, a simple search will provide the files you need.
If it's not a driver issue, I really don't know what it could be. But I would definitely try reinstalling the appropriate drivers first.
Click to expand...
Click to collapse
I'm using a samsung firmware and i installed kies recently, though even after i installed it, the USB connection was still working for i while until it stopped.
should i reinstall the kies?
Nezys said:
Go to Settings>Applications>Development and if USB debbugging is flagged,deflag it!
Click to expand...
Click to collapse
It was deflagged, but thanks anyway
abialystok said:
I'm using a samsung firmware and i installed kies recently, though even after i installed it, the USB connection was still working for i while until it stopped.
should i reinstall the kies?
It was deflagged, but thanks anyway
Click to expand...
Click to collapse
Try with a different USB cable.
Sent from my GT-I9000 using Tapatalk
Try to reinstall Kies or one of the steps that I've read here:
http://www.androidgalaxys.net/suite...problemi-connessione-collegamento-usb-galaxy/
Translated:
Make sure you have installed the latest version of Kies (currently 2.0.1).
For owners of Windows Vista / Seven Kies launch in admin mode
Connect your phone to your PC using the default launcher from Samsung (TouchWiz)​​. Alternative launcher may not be recognized by Kies. Close any programs in the background on your phone and PC.
Make sure that in Settings> Wireless and Networking> USB Settings is selected Samsung Kies or Ask the connection.
If you already selected, try to choose any item and then set one of the two mentioned.
Try using another USB port on PC. Not all USB ports may be able to deliver the power needed to power the device.
Restart both the phone and your PC.
Try reinstalling the drivers of the Galaxy. To do this open Kies, go to the Tools menu and then install drivers.
Try using another USB cable.
ok, I tried everything but switching cable coz i know it works...
here's the weird thing: I tried connecting my phone to 3 different computers, 1 worked and the other 2 (including mine) didn't work.
the thing is that the other computer that didn't work and the computer that did work never touched a Samsung before, so basicaly i have no idea what would make one of them work and the other not to work.
I'm really confused.
Try going into device manager and see if there are any devices flagged with '!'
If not, find your samsung device from device manager, and uninstall it and delete all drivers, then reinstall them.
Try that. It may just be a windows issue, I've had similar problems before but not even with a phone, but a flash drive.
well, tonight the computer restarted itself because of some updates, now it seems to magicaly work, even though i restarted it before.
i have no idea y it suddenly started working, but i can only hope it wouldn't happen again.
thank you all, you guys are great!

Gear not recognized by MobileMe wondershare?

Hi;
Just got my refurbished gear watch 1 from BB and everything working as normal. I am using a windows PC, Gear has software V700XXUBNA6, model SM-V700 but when I plug via USB to windows PC, it does not recognize it nor do I get the screen on the watch to check off for access. This is the same software I used on my previous gear watch and was able to load ringtones, apps, songs and movies.
Any advise will be appreciated.
Tia,
Ian B
Perhaps you have tried these already, but I need to ask:
- does the computer recognize the new gear, ie do you hear a sound when you plug in the usb cable?
- If so, does any other programs recognizes the new gear, like does Kies recognizes it, or does ODIN recognizes it when you put it in download mode?
- maybe try a diff usb cable, or diff usb port, or perhaps even a diff computer, ie win7 instead of win8?
Sorry if I am being a little nit-picking , it may not be your wondershare program, I know the usb port on the cradle can be very loose on some units, so your situation could be hardware rather than software.
bballengphd said:
Perhaps you have tried these already, but I need to ask:
- does the computer recognize the new gear, ie do you hear a sound when you plug in the usb cable?
- If so, does any other programs recognizes the new gear, like does Kies recognizes it, or does ODIN recognizes it when you put it in download mode?
- maybe try a diff usb cable, or diff usb port, or perhaps even a diff computer, ie win7 instead of win8?
Sorry if I am being a little nit-picking , it may not be your wondershare program, I know the usb port on the cradle can be very loose on some units, so your situation could be hardware rather than software.
Click to expand...
Click to collapse
Yes, tried most already. This is the same PC I rooted previous gear w and has MobileMe installed for loading songs, ringtones etc.
Yes, I get ping when I plug tp PC but, not the screen that u check off in gaer to sync w MobileMe.
Will put in download, test Odin and report back.
Gonna try new cable and report back.
Will keep trying and report back as I go.
Ian B
bballengphd said:
Perhaps you have tried these already, but I need to ask:
- does the computer recognize the new gear, ie do you hear a sound when you plug in the usb cable?
- If so, does any other programs recognizes the new gear, like does Kies recognizes it, or does ODIN recognizes it when you put it in download mode?
- maybe try a diff usb cable, or diff usb port, or perhaps even a diff computer, ie win7 instead of win8?
Sorry if I am being a little nit-picking , it may not be your wondershare program, I know the usb port on the cradle can be very loose on some units, so your situation could be hardware rather than software.
Click to expand...
Click to collapse
Latest testing, still can not get MobileMe to recognize it after 3 diff USB cables and 2 USB ports on windows Xperia computer.
Installed windows kies3 and recognized it , was able to to load movies and song to kies 3. Not sure if inside the gear since kies3 did not have an option to load apk. If someone can link me or write down the steps for side loading apks in windows, it may solve problem for now and able to see if the songs and movies went into Gear or not.
If I have no luck, will watch Google io next week for Moto360 and return the Gear.
Ian B
Couple more suggestions, you may have already tried these though:
- Your gear appear to be stock, no root no null-rom, is that correct? Did you enable usb debugging?
- did you try using mobileMe after Kies recognized it?
- you can use adb to sideload apks to the gear, but you will need to root the gear first, and install a custom recovery, there are instructions in the General section on how to adb push to the gear.
Don't worry about rooting and custom roms, you can go back to stock after rooting, and there will be no trace of rooting left.
Sorry to hear about your troubles, hope things change for you soon. Good luck.
bballengphd said:
Couple more suggestions, you may have already tried these though:
- Your gear appear to be stock, no root no null-rom, is that correct? Did you enable usb debugging? Correct, stock uprooted, USB debugging checked.
- did you try using mobileMe after Kies recognized it? Tried but it fails after rebooting PC post kies install.
- you can use adb to sideload apks to the gear, but you will need to root the gear first, and install a custom recovery, there are instructions in the General section on how to adb push to the gear. So I need to root gear to side load apks w adb, correct?
Don't worry about rooting and custom roms, you can go back to stock after rooting, and there will be no trace of rooting left. Ok but, I believe in the past that every time gear manager updated, all the side loaded apks would get whipped out and had to re install.
Sorry to hear about your troubles, hope things change for you soon. Good luck.
Click to expand...
Click to collapse
Thanks for your help, put responses next to each question. Will keep trying and report back.
Ian B
Mr Ian B said:
Thanks for your help, put responses next to each question. Will keep trying and report back.
Ian B
Click to expand...
Click to collapse
Thanks for the detailed response.
Yes you do need root for adb to work.
There were quite a bit of discussions of apps disappearing after gear manager updates, especially sideloaded ones, on both null roms and stock rooted gears. The apps are still there on the gear, its just that the updated gear manager will not recognize them being on the watch for some reason. I think some were advising using either a specific gear manager version or even older roms if you wanted to keep everything there and working.
Personally I think its Samsung's way of trying to keep things controlled by themselves, in a similar fashion to what Apple did with their ios.
Gear not reconized by adb or mobileme wondershare
I updated my galaxy gear to latest version and since then adb is not recognizing it. I tried almost everything, changing cable, restarting, usb debugging on/off, i have no idea what could it be. ADB always returns an emtpy list on "adb devices" and error:no device on adb:shell. Any idea?

help? Certainly not a pro, but not entirely a noob... so basically a noob...

Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
AlkaliV2 said:
You need to tell us what OS you're using, what software you installed prior to plugging it in, if you made a TWRP backup before you jumped to CM12.1, if you have an understanding of ADB commands or if you used WugFresh to do all the unlocking and installation steps. Just list anything you think would be pertinent. More information is always better than less.
Click to expand...
Click to collapse
So, I've been on stock until I switched over to CM12. I do have a twrp backup but apparently only did that after I moved to CM12. I have only the most basic (read basically nonexistent) understanding of ADB, and can follow directions I find online but no real knowledge as to how anything works. I also did not use wugfresh, but unlocked via ADB and rooted via chainfire. Honestly, I followed most of the direction I found on youtube via a creator called wwjoshdo (I'd link but I'm not allowed).
Otherwise that feels like the info. I didn't fiddle with my nexus until I started have battery issues and then decided to unlock/root/flash, and that was about 6 weeks ago. I'm also running what standard apps for a rooted device on CM12, flashify, cyandelta, setcpu, and, Titanium Backup. Help?
llawhsoj said:
Hey there folks,
So I unlocked, rooted my Nexus 6, and then flashed Cyanogenmod12. So far pretty happy, but I was thinking about switching back to play around with Marshmellow, but ran into a problem. My nexus doesn't seem to want to connect with my pc anymore... kind of.
I did the normal thing, USB debugger is on and I updated drivers through SDK but then when I plug it in I'll still occasionally get an automatic prompt that tries to install drivers and stalls. I do cannot find my device listed anywhere when it is plugged into my pc, but I do here the beep that let's me know it is connected (and the device is charging).
I CAN get it to connect via PTP but cannot get anything to happen with MTP.
So I'm stumped. Feels like the hardware is working but I'm running into driver issues, but... well I don't know.
Help? Please?
Click to expand...
Click to collapse
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
RMarkwald said:
Are you using Windows 10? If so, I have that same issue with MTP, however, fastboot/adb commands will still work.
Click to expand...
Click to collapse
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
llawhsoj said:
Yup, should mentioned that. I am on 10. (And I'm just realizing that's what AlkaliV was asking about!) I'm on 10 home, 64 bit.
Well good to know that I'm not alone. So here is a question, if you are getting abd to work and I don't know how to use abd really. Anyone have a tutorial you'd recommend to help me figure out how to use it?
Or care to help me figure out how to use abd?
Click to expand...
Click to collapse
So this link will get you up and running with ADB (if it isn't already working): http://forums.team-nocturnal.com/index.php?/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10-updated-9-11-2015/
These are the most common commands that are used with ADB once you get it installed. Also, an excellent way to pull a log from the command prompt: http://developer.android.com/tools/help/shell.html
Assuming you can see the device once you pass the command, "adb devices" it means you are connected but the MTP driver hasn't been loaded properly. I had to fix this by cycling Android debugging and ADB notification in developer's option until Windows was like, "Hey! There it is!" Also, MTP works properly for me when booted into TWRP so if you desperately need to transfer a file you can do it from the TWRP recovery menu.
Noob Tip/Reminder: Make sure that when you plug it in the first time you change it from 'Charge Only' to MTP and if things still seem quirky reboot Windows. It's all just a game of getting it recognized at this point.

Categories

Resources