i flashed Cyanogenmod7 recently and also decided to learn a bit about adb about the same time... i got to "type adb shell" in someone's adb guide but i keep getting the error "no device found"...
i also odined to stock this afternoon and when i tried the same thing, adb recognized it right away.
to satisfy curiousities, i can confirm 100% that debug is on, my cable is good and ive tried several diff usb ports as well as rebooted both my computer and phone.
adb worked with stock JFD 2.1 and stock 2.2 KB5, gave me the error in cyanogenmod 7.1.0 RC1
thanks in advance
You're going to need to use the android sdk to get the nexus s driver.
Google nexus s driver, and there'll be instructions from Google on how to get it installed.
Sent from my SGH-T959 using XDA App
Sweet thanks
Sent from my SGH-T959 using XDA App
Related
i been rooting phones since i knew how which has been like 3 years! and this epic has been by far the biggest poin in my ass.. i have tried everything in my power ot get it rooted i have read every thread about the one click root and all that but heres my problem ... my phone recognizes my phone when i do not have usb debug on soon as i click it on it puts a up a screen that says need to fine files like me put them manually or windows scans for it .. i have tried everything even going to the drivers and manually updating them and no go !! i have uninstyalling and install tried putting phone back to factory reset ! and still no go .. just keep getting device not found on the run run bat ... please help! i have thread after thread and ive tried it all dont know what to do ..
are you trying to do the one click in recovery?
No I'm doing exactly what is says on page one.. I downloaded the drivers . Then. I put on debug mode then plug in and do the run and it says device not found... am I suppose to do in recovery.. or what.. tried it at my work to and no go
Sent from my SPH-D700 using XDA App
try downloading and installing the android sdk, this fixed this issue for me, just make sure to install the components for android 2.1 etc... PC recognized right away after this:
http://developer.android.com/sdk/index.html
Thanks I will try this !!!
Sent from my SPH-D700 using XDA App
I k ow my computer had probably with certain USB ports don't know if that's your prob but that personally took me a while to figure out and I was pissed like no other
Sent from my SPH-D700 using XDA App
Once you have sdk installed, if you're having trouble connecting your phone to your computer, get "adb wireless" from the market and you can connect that way leaving no need for the usb cable. All you need is your phones wi-fi turned on and a know how of adb.
Sent from my SPH-D700 using XDA App
BThomas22x said:
Once you have sdk installed, if you're having trouble connecting your phone to your computer, get "adb wireless" from the market and you can connect that way leaving no need for the usb cable. All you need is your phones wi-fi turned on and a know how of adb.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
You have to have a router too. A way that both the computer and phone can connect.
Yeah... Thanks
Sent from my SPH-D700 using XDA App
Well.. it seems to me that there has been an unusually high amount of people who are now getting the USB device not recognized error when plugging their phone into their computer. Myself included. I'm stuck on dj05 because of it.
Can everyone that's having this problem post what they've flashed and how? Or any other problems their having? Make sure to post what OS you are using, x64 or x86, stock cord or not, Samsung drivers version, etc. Maybe we can find a common theme between everyone having the problem, and figure out a way to fix it. Thanks!
Sent from my SCH-I500 using XDA App
I will asap when I get home to my computer. Thanks for the thread as I have asked myself, but still no luck.
Sent from my SCH-I500 using XDA App
Same problem. I was running DL30 with the Blackhole Rom. Just stopped working yesterday. Tried flashing stock, then DL05. Can't root, ADB doesn't see it, nothing. Can't mount either. Win7 64 keeps saying its a CD drive and tries to install the verizon drivers. Did that, still tries.
I thought considering I started the thread, I should probably post my configuration as well. I had no problems with USB until I flashed kaosinate. I'm sure this didn't have anything's to do with it but oh well. I also flashed the lasted kaosinate kernal. After that, I installed superclean with adryn.'s test kernal. Still nothing. If you look around, there are definitely quite a few reports of the phone being recognized as a CD drive. Adrynalyne reccomends flashing one of his new test kernals which has been reported by some to fix the problem. He says that he still has to reboot with the phone plugged in to have it recognized, however.
I an running windows 7 pro x64 with the lastest Samsung drivers. I only get the USB error when plugging the phone in while its In downlaod mode. Otherwise it is recognized as a CD drive. I guess this is what we get for flashing non stock firmware, Roms, etc. If anyone has any suggestions, feel free to post them.
Sent from my SCH-I500 using XDA App
Randomly came back...flashed stock DI01, then DI05, then DI09, then back to DI05. Working now...it must have finally wiped some bad code or something...
OK, so I went to root the thing...when the root rebooted, it didn't work. I had to disconnect and reconnect the USB cable to get it to recognize again.
Did you use Odin? Where did you get the files from?
Sent from my SCH-I500
Running Windows 7 64bit
running super clean 3.2nv
I finally got it to recognize. But it will not recognize when i boot into download so i can flash with odin...
I've gotten a new nexus 7 in the mail today and the first thing that I tried to do was unlock the bootloader and root the device to flash custom kernel and ROM. but i ran into a problem in the first step. Im having no luck with the drivers at all. i have searched and tried everything. I have tried this 1.5.2 toolkit and watched the video. In the section that i have to go to device manager and manually install the drivers, i didnt get anything. i downloaded the driver from asus themselves and it worked (pictured below) but when i try to use adb commands, nothing happens. I also installed the 64 bit drivers and it gives me the same thing as the picture and when i run the toolkit, it doesnt find adb. Can anyone help out please? and yes, i have enabled usb debugging, just in case you wonder.
What OS are you using?
When you plug the Nexus in the USB port does anything happen?
Have you rebooted the workstation?
4.1.1 jellybean. I've rebooted several times. When I plug it into the computer, my computer makes the regular "New device" sound and then it searches for the nexus driver but cannot find it. The tablet shows debugging connected.
Sent from my Gameboy Color
You have a workstation with JellyBean on it? I'm guessing it is a Win box perhaps right? Have you rebooted it?
I just unlocked and rooted today. I downloaded and installed the drivers from the PDAnet website. Everything worked fine. Hope this Info helps you get you unlocked and rooted
Sent from my Rooted Nexus 7 using xda premium
krelvinaz said:
You have a workstation with JellyBean on it? I'm guessing it is a Win box perhaps right? Have you rebooted it?
Click to expand...
Click to collapse
Sorry no, I misunderstood. I don't have a workstation. I have a laptop running Windows 7 and the tablet is running jelly bean.
Sent from my Gameboy Color
speedygonzo said:
I just unlocked and rooted today. I downloaded and installed the drivers from the PDAnet website. Everything worked fine. Hope this Info helps you get you unlocked and rooted
Sent from my Rooted Nexus 7 using xda premium
Click to expand...
Click to collapse
You went to pda net website and downloaded a .exe file and ran it right? I guess I'll have to do it from another computer maybe. I just don't have one though. I'll keep trying
Sent from my Gameboy Color
See my driver advice in http://forum.xda-developers.com/showthread.php?t=1794203
osmosizzz said:
You went to pda net website and downloaded a .exe file and ran it right? I guess I'll have to do it from another computer maybe. I just don't have one though. I'll keep trying
Sent from my Gameboy Color
Click to expand...
Click to collapse
Yeah, just download the driver package you need for your laptop and install them. The .exe is more like a setup/installation wizard for the drivers.
Sent from my Nexus 7 using xda premium
Napalm2 said:
See my driver advice in http://forum.xda-developers.com/showthread.php?t=1794203
Click to expand...
Click to collapse
Still nothing. I keep getting the android composite ADB interface driver no matter where i install the driver from and i've uninstalled and deleted the driver various times.
speedygonzo said:
Yeah, just download the driver package you need for your laptop and install them. The .exe is more like a setup/installation wizard for the drivers.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
still the same android comosite ADB interface
I was finally able to unlock the bootloader in Linux. But ran into another annoying problem
Sent from my Gameboy Color
I'm not able to use fastboot at all on my nexus 4
I always get:
< waiting for device >
adb works fine, I can shell and view all the files etc. and "adb devices" lists my phone there and doesn't say offline. I've done all the normal stuff like changing USB ports (2.0 and 3.0) and I've tried different versions of ADB and the driver, clearing the RSA keys on the device. The phone is totally stock, no root and running 4.3 / JWR66Y and this has been happening before the latest OTA (JWR66Y) update (first OTA of 4.3)
Here's my bootloader info
Command line: console=ttyHSL0,115200,n8 androidboot.hardware=mako lpj=67677 uart
_console=enable lcd_maker_id=primary lge.hreset=off lge.reset=mode_reset gpt=ena
ble lge.kcal=0|0|0|x lge.rev=rev_10 androidboot.emmc=true androidboot.serialno=0
0475fbe14129674 androidboot.bootloader=MAKOZ20i androidboot.baseband=mdm bootrea
son=reboot
and I'm currently using the "Android Composite ADB Interface" Rev8 driver from the SDK on Windows 7 x64 along with the 18.0.1 version of the platform tools.
Did you download the fastboot.zip and place it in platform-tools of the android SDK?
Sent from my Nexus 4
Try the SDK package ..
Sent from my MB886 using xda app-developers app
I'm using the fastboot binary from the SDK as stated in the OP
I know this may seem obvious but covering the basics. You installed the fastboot driver? Is phone seen at all via device manager?
Sent from my Nexus 4 using xda app-developers app
marsdta said:
I know this may seem obvious but covering the basics. You installed the fastboot driver? Is phone seen at all via device manager?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do you mean the ADB driver or something else, I've tried the naked ADB driver and the SDK ADB driver, both give the same result, ADB.exe connects, I can open a shell and see the files etc., but fastboot.exe just hangs on waiting for device
When you plug in phone and its in fastboot is it recognized by device manager? Do you see an exclamation point next to it. If so you have to click and choose update driver(I used sdks version)
Sent from my Nexus 4 using xda app-developers app
marsdta said:
When you plug in phone and its in fastboot is it recognized by device manager? Do you see an exclamation point next to it. If so you have to click and choose update driver(I used sdks version)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No problem there. I don't think ADB would work if the driver weren't working would it?
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app
Delete.. Dndnt read OP properly.
marsdta said:
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes I've reinstalled the driver a few times and tried different drivers. I've tried the universal naked 0.72.the rev8 from the SDK and Koushes, all 3 work with adb and none worked with fastboot
marsdta said:
It would still work. Technically the driver is installed twice even though its the same. Once while phone is booted up and once while in bootloader.
Have you tried reinstalling the driver? after updating to 4.3 I had issues with adb and fast boot. I had to reinstall the drivers and all went back to normal
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Which driver did you use in the end? I've tried just about everything, I even grabbed another nexus 4 and I'm having the same issue with that one (which is on the earlier 4.3 OTA update btw)
Download the fastboot.zip and place it inside platform tools, even though SDK shows fastboot download fastboot again and place it inside
Sent from my Nexus 4
Cream$ickleHJ said:
Download the fastboot.zip and place it inside platform tools, even though SDK shows fastboot download fastboot again and place it inside
Sent from my Nexus 4
Click to expand...
Click to collapse
Download from where? Which files do you suspect are missing?
I used the one from the SDK. When booted up device manager shows adb composite and when in boot loader device manager shows android boot loader interface.
When you are reinstalling the drivers did you uninstall them first. That's what I usually do. Once helped someone who had the driver installed several times, so they were conflicting . I would uninstall drivers and delete any mention of them. Reboot PC. When plug in phone I ignore it trying to search and install boot loader driver. And install it manually
Sent from my Nexus 4 using xda app-developers app
can anyone tell my y my adb does not see my device?? i downloaded the drivers that i believe were the ones for the vs980, if those are the wrong ones please tell me.
i still managed to get root but now i need to push recovery but it doesnt see my device....
Lg stock drivers don't seem to help pc to see phone in recovery I installed pdanet and downloaded lg drivers through it and now adb works.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
Lg stock drivers don't seem to help pc to see phone in recovery I installed pdanet and downloaded lg drivers through it and now adb works.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I owe you more than that thanks. This is incredibly useful info!
Backstory:
Flashed 800 radio on 802 (curiousity...)
Didn't have 802 radio on device to flash back
802 in bootloops
google usb drivers wouldn't install
@lingarajug saved my sanity and taught me something
I love how much I can learn on xda-dev...
Hahahahahhahahaha they say curiosity killed the cat, I was in the worst situation like you were but I tried copying new Rom and gapps to sdcard and flash and went into recovery and curiously cleaned everything in advanced wipe and left with phone with no Rom to boot and no file to flash I did sleep all night and finally my old ideas came through and found pdanet and since then have been spreading this message around, glad that it helped u.
Sent from my LG-D800 using xda app-developers app