Hey.
I'm currently on Cyanogenmod 10.1 and I am developing an app for college using Eclipse.
My phone wont get picked up by Eclipse when I try to run it on the phone.
Kies doesn't detect my phone no matter what storage mode it is in.
So how can I fix this?
Or is it unsupported with Cyanogenmod?
Also I tried USB debugging, you enable it by clicking on the Cyanogenmod build several times, still doesn't work.
Any help would be sweet!
I don't know about eclipse, but i know only stock works with kies
Sent from my gt-9100 powered by dorimanx
You can thank me if i helped you
AndyOHart said:
Hey.
I'm currently on Cyanogenmod 10.1 and I am developing an app for college using Eclipse.
My phone wont get picked up by Eclipse when I try to run it on the phone.
Kies doesn't detect my phone no matter what storage mode it is in.
So how can I fix this?
Or is it unsupported with Cyanogenmod?
Also I tried USB debugging, you enable it by clicking on the Cyanogenmod build several times, still doesn't work.
Any help would be sweet!
Click to expand...
Click to collapse
Have you tried installing the usb drivers for your phone?
Sent from my SCH-I535 using xda premium
Ah only stock works with Kies?
Maybe I won't be lucky then.
And yeah I even just reinstalled the drivers there.
Would make it so much easier if I could simply run the program straight off my phone rather than have to compile it every time in Eclipse.
AndyOHart said:
Ah only stock works with Kies?
Maybe I won't be lucky then.
And yeah I even just reinstalled the drivers there.
Would make it so much easier if I could simply run the program straight off my phone rather than have to compile it every time in Eclipse.
Click to expand...
Click to collapse
Another possibility is that considering CM 10.1 is still in nightly build stages (Even with the M2 release) and not a final product it's possible that the USB debugging connection may not be playing nice with your computer, does ADB recognize your phone? Does the computer recognize the device at all? The other possibility is to compile the program with eclipse, then after eclipse compiles it locate the compiled program, and push the compiled program to your phone to test it out. Also the reason it has to compile in eclipse and not just run off the phone, is that the Java and XML code (Among other things) that make up the program must be compiled into a .apk package file so Android can read and run the program. If the Java and XML code was left uncompiled and just ran off the phone Android wouldn't be able to run the program.
Yeah I used to compile and push them onto the phone but my friend showed me his S3 running straight off eclipse.
And yeah the PC picks up the phone and I can put files on it no problem. What is the ADB thing?
AndyOHart said:
Yeah I used to compile and push them onto the phone but my friend showed me his S3 running straight off eclipse.
And yeah the PC picks up the phone and I can put files on it no problem. What is the ADB thing?
Click to expand...
Click to collapse
Is your friend's Galaxy S3 rooted and is it running as custom ROM? And to answer you question ADB stands for Android Debug Bridge (Part of the Android SDK) it is an extremely helpful tool that allows you to communicate with your Android device and issue commands to it either by attaching it your computer through a USB cable or wirelessly using Wifi. One of the things you could do with ADB is push the compiled apk file to your device without having to hook the device up to your computer through USB every time you want to test out a new build of your application. You can learn more about ADB from here. You can download the Android SDK which allows you to install ADB from here.
shimp208 said:
Is your friend's Galaxy S3 rooted and is it running as custom ROM? And to answer you question ADB stands for Android Debug Bridge (Part of the Android SDK) it is an extremely helpful tool that allows you to communicate with your Android device and issue commands to it either by attaching it your computer through a USB cable or wirelessly using Wifi. One of the things you could do with ADB is push the compiled apk file to your device without having to hook the device up to your computer through USB every time you want to test out a new build of your application. You can learn more about ADB from here. You can download the Android SDK which allows you to install ADB from here.
Click to expand...
Click to collapse
No his phone isn't rooted it's just stock jelly bean.
So that means that Cyanogenmod is what is stopping it from working I take it?
I will have a look at the ADB thanks man!
AndyOHart said:
No his phone isn't rooted it's just stock jelly bean.
So that means that Cyanogenmod is what is stopping it from working I take it?
I will have a look at the ADB thanks man!
Click to expand...
Click to collapse
Glad I could help, Cyanogenmod may be causing it from not working as some apps and other services are sometimes incompatible or have issues on devices running Cyanogenmod.
Related
There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
SysAdmNj said:
There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
Click to expand...
Click to collapse
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Entropy512 said:
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Click to expand...
Click to collapse
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
SysAdmNj said:
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
Click to expand...
Click to collapse
if you are on CM7, i think you need to install the nexus S drivers, which are included in the Android SDK. you will need to run the emulator and run the update in SDK
Since you mentioned this has happened on two different computers, I doubt my advice will help. With that said, whenever I've had issues like this, I've found that USB ports tend to be the culprit. Have you been using ports on the front of a tower? Have you tried the ones on the back as well? Again, just taking a shot at a possible fix...
This is weird but I can't seem to figure it out. I have a rooted S2 CWM, CM7 and I am trying to pull wakelocks using adb. Now I used adb last week but now for some reason Windows 7 64x will not recognize my phone. I've re-installed the official driver from Samsung, uninstalled Kies and re-installed, rebooted, re-installed Android SDK...nothing seems to work. Not sure what else to do. I can put it in USB mode and it works but just straight plugging the phone up doesn't work. Turning on USB debugging does nothing. Any help would be appreciated.
Only thing I can tell you is keep trying to uninstall the driver and re installing it until it works - if you have ever considered using LINUX such as dual booting it or installing it on an older machine you have setting around this is one good reason to take that step, you will not likely ever have any trouble getting LINUX to recognize your phone.
Adb works great, and LINUX is the native development platform form Android.
Sent from my SAMSUNG-SGH-I777 using XDA App
dayv said:
Only thing I can tell you is keep trying to uninstall the driver and re installing it until it works - if you have ever considered using LINUX such as dual booting it or installing it on an older machine you have setting around this is one good reason to take that step, you will not likely ever have any trouble getting LINUX to recognize your phone.
Adb works great, and LINUX is the native development platform form Android.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
I've tried that a couple of times. I do have a laptop at home with Ubuntu so maybe I'll just hook it up to get the information. Just not sure why this won't work when it was yesterday.
ive tried every method to unlocking the bootloader and i cant get the command prompt to do anything it wont reconize my device is their an easier way into unlocking and rooting
If you can't get adb working then you shpuldnt have a rooted phone in the first place.
Sent from my HTC6435LVW using xda app-developers app
Sounds like you don't have all the drivers installed and/or don't have sdk tools installed.
And no, there is no other way to unlock it.
orangechoochoo said:
Sounds like you don't have all the drivers installed and/or don't have sdk tools installed.
And no, there is no other way to unlock it.
Click to expand...
Click to collapse
Download the latest SDK (search for 'adt- bundle -windowsx86') and extract that file into your C drive.
There will now be an 'adt-bundle-windowsx86' folder on your C drive, inside that is the SDK manager.exe
Run SDK manager-it will create the adb tools you will need AND put them in the "sdk/platform-tools folder"
after the SDK tool opens, you only need to add the 'google usb drivers' (1 item) No need to select that box
as is checked off by default anyway. All other required adb files will have installed already. Install those google drivers
and you should be ready to unlock the bootloader. I would put all the OTHER required files to unlock it in the 'platform-tools folder also.
Then go to that platform-tools folder, hold down shift key and right click in an open area, choose 'open command prompt here' then just follow the tutorial pasting in the commands.it will work...
Jduncan312 said:
ive tried every method to unlocking the bootloader and i cant get the command prompt to do anything it wont reconize my device is their an easier way into unlocking and rooting
Click to expand...
Click to collapse
This work perfectly for me http://forum.xda-developers.com/showthread.php?p=34582289
https://www.youtube.com/watch?v=glGdw2HAumg&feature=youtube_gdata_player
I followed this video to get sdk installed
Thats the same vid that i used too and it work just fine for me, did you also changed your local variable like the vid, also on your phone make sure you have usb debugging enabled
Gungrave223 said:
Thats the same vid that i used too and it work just fine for me, did you also changed your local variable like the vid, also on your phone make sure you have usb debugging enabled
Click to expand...
Click to collapse
I'm not the one with the problem, I'm already unlocked, rooted, and rommed
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
I had a issue with the drivers installing from my phone to my pc. I installed pdanet 3.5 (Google it for pc, play store for phone) on my pc and phone. Let pdanet install the drivers, once installed you can uninstall pdanet.
Once the drivers installed I was able to see my device in adb. Sorry if one of the links above were for this fix I didn't click them.
HTC DROID DNA
orangechoochoo said:
I'm not the one with the problem, I'm already unlocked, rooted, and rommed
Click to expand...
Click to collapse
Lol yea i know i was just saying that that method work for me too.
Jduncan312 said:
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
Click to expand...
Click to collapse
Well if you type the command adb device and nothing and your device doesnt show, there is 2 possible reason for the issue the first is that your phone is not in adb mode, go to the setting/developer options and make sure usb debugging is enabled
the second is that your phone adb driver weren't installed correctly i had the issue when i watch this video because when i was in sdk manger i unchecked the option to install the android 4.2 (API17) package, disconnect/reconnect phone and the adb driver install just fine after that
Sadly there is no other way to remove the verizon cid block as of right now
Jduncan312 said:
ive already gotten the sdk installed ive watched droidmodderx video on how to do it and still cant get no where im new to rooting htc phones ive done rooted motorola and samsung phones and their not as hard
Click to expand...
Click to collapse
If you have sdk installed right then adb will be working...then if you follow the tutorial in the dev section (jcase) it will work. I have heard that some older versions of adb didn't support restore and that WAS an issue for me so I re installed the latest version of SDK and it then worked flawlessly. That's why I suggested getting the latest version and reinstalling. Maybe not the problem but you have had no luck with your old version so why not. You need to go slowly and read carefully. The process is really 3 sections, bootloader fix, official HTC website unlock code process and then rooting itself. It takes a while but it's how everyone got there, some easier than others.
Was wondering why I cannot connect my phone to the computer after installing the Rom Unofficial 10.1
The computer saw my phone before the install but not anymore. I have the latest version of Kies just
wondering why the computer doesnt see the phone anylonger. Suggestions?
nitrohelipga said:
Was wondering why I cannot connect my phone to the computer after installing the Rom Unofficial 10.1
The computer saw my phone before the install but not anymore. I have the latest version of Kies just
wondering why the computer doesnt see the phone anylonger. Suggestions?
Click to expand...
Click to collapse
Does your computer not show it in device manager or does it not show up under Kies?
Had same issue here had to put SD in different phone to put new ROM on it.
Sent from my SAMSUNG-SGH-I717 using xda premium
This is a couple days old.
However For future reference...
Aosp roms sometimes require the vanilla drivers not the ones for the I717.
Just install the android sdk (WHICH SHOULD BE A STEP DONE BEFORE EVER TOUCHING YOUR PHONE) the drivers are within.
Then when you plug in it should read it as an android debugging device. And a mass storage device.
I have a new S4 with baseband MK2. I am getting ready to do the root etc. but I was testing ADB first to make sure it works.
I have installed the latest USB drivers, and turned debug on in the S4
I get get adb to launch, but when I use the command "ADB devices" nothing shows up.
I have rebooted both PC and phone with the same results.
Question,
Does the phone need to be rooted before ADB will work? If so....then how to I side load "Towelroot"? or anything else for that matter.
am I missing some sdk files...or something else?
Thanks
wetwaterdog said:
I have a new S4 with baseband MK2. I am getting ready to do the root etc. but I was testing ADB first to make sure it works.
I have installed the latest USB drivers, and turned debug on in the S4
I get get adb to launch, but when I use the command "ADB devices" nothing shows up.
I have rebooted both PC and phone with the same results.
Question,
Does the phone need to be rooted before ADB will work? If so....then how to I side load "Towelroot"? or anything else for that matter.
am I missing some sdk files...or something else?
Thanks
Click to expand...
Click to collapse
Usually when nothing shows up at all it's a driver issue. What drivers did you install where did you get them. Windows right?
Edit : root not required.
jawmail said:
Usually when nothing shows up at all it's a driver issue. What drivers did you install where did you get them. Windows right?
Edit : root not required.
Click to expand...
Click to collapse
Got the drivers from samsung site...latest ver 1.5.45. phone connects to windows computer and displays directories so I know the USB driver is ok.
I did some more looking and am updating my sdk devices right now. I expect that to correct the problem.
wetwaterdog said:
Got the drivers from samsung site...latest ver 1.5.45. phone connects to windows computer and displays directories so I know the USB driver is ok.
I did some more looking and am updating my sdk devices right now. I expect that to correct the problem.
Click to expand...
Click to collapse
Drivers are good then, update your SDK like you said and try again. It should work after that, I don't have an S4 but they're all the same when it comes to ADB and fastboot. Good luck.
jawmail said:
Drivers are good then, update your SDK like you said and try again. It should work after that, I don't have an S4 but they're all the same when it comes to ADB and fastboot. Good luck.
Click to expand...
Click to collapse
Yup....sdk's installed and all is well.....
I sure wish I knew exactly which downloads to take from the SDK download manager....
I played it safe with the 4.3 and 4.4. I didn't know if the updates were progressive (included all past needed stuff) or just specific for the version.