Hey all, just started a new project in Eclipse, selected Android 2.1-update1 as the SDK, and I went to debug it but it cant find my EVO to debug on. Did I select the wrong SDK? USB debugging is enabled.
I think this belongs to the Q&A section.
Despite that, I don't think I can help you, I will let one of the smarter individuals answer your question.
Mast3rpyr0 said:
Hey all, just started a new project in Eclipse, selected Android 2.1-update1 as the SDK, and I went to debug it but it cant find my EVO to debug on. Did I select the wrong SDK? USB debugging is enabled.
Click to expand...
Click to collapse
Can you connect through ADB?
You must be sure that you have the proper USB drivers installed first, and then go into the AVD/Devices manager in Eclipse, and you should then be able to see it as an available device. If you can't see it as an available device, then you probably can't connect to it through ADB. Same applies in reverse...if you can do it in ADB, you should be able to in Eclipse.
The SDK version isn't terribly important, you can make it work with a little elbow grease, but 2.1 should be fine.
I'd be glad to help you troubleshoot this if you continue to have issues.
I also like seeing this in here because it's a part of Android Development, as this section isn't necessarily devoted solely to ROM development. But that's just my opinion
Ahh silly me, I have not installed any USB drivers for it. Downloading HTC sync now which I guess has those drivers. Thanks for the Help
EDIT: Everything's working now, Thanks!
Mast3rpyr0 said:
Ahh silly me, I have not installed any USB drivers for it. Downloading HTC sync now which I guess has those drivers. Thanks for the Help
Click to expand...
Click to collapse
Sure, no prob!
Related
I am currently running Froyo 2.2 Red Glass Nov 2 Update using the Firerat Partition Mod. I am using Windows 7 Ultimate and I can't get ADB to work. It's something with the drivers. Does anyone have the drivers needed to get ADB working on Windows 7. I think it may be the updates Windows pushed down but it could be something else. Also I wanted to know, if there's a way to flash a recovery without using adb. My recovery is f*cked...I had RA-1.7 (Darch Unofficial) working properly, but wanted to see what was the benefit of using ClockWorks and I went from Clockwork to 1.6.2 and now I can't boot into recovery at all. If you need a log let me know. Thanks!
SN: I know this is in the wrong forum but I can't get my phone to boot into recovery nor use adb on my pc to flash a new recovery image. I need help because I'm gonna go crazy...AAAHHHH...wouldn't you do the same for your Hero???...lol...but seriously, I need help like yesterday if anyone has a solution please PM me or post. Thanks Guys...
I can't remember why but that happened to me. I'm running windows 7 64 bit. Try using the flash_image command and push a new recovery I always use amon ro 1.6.2. You can do that from terminal on your phone if you have to. I don't know if your s-off but if worse comes to worse then you could use a HERCIMG.zip Also another guy wrote about this in the q&a section. But it could have been deleted. I remember I ended up running the ruu at the end. It's not the computer it's the phone
WOW..you really need to search and put this in the right section. you even knew this was the wrong section and only posted cuz its a busier section!!
If you would have just even looked through this section a bit you wouldve found this thread that has the drivers.
http://forum.xda-developers.com/showthread.php?t=832240&highlight=drivers
Read this also it will help
http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/
As for your problem im sorry i cant help you out but if you post in the Q&A section like your supposed to then im sure someone there can figure it out. Possibly IMPALER as he seems to be on alot.
Good Luck with finding something out.
Correction for ^^^
t12icky0 said:
WOW..you really need to search and put this in the right section. you even knew this was the wrong section and only posted cuz its a busier section!!
If you would have just even looked through this section a bit you wouldve found this thread that has the drivers.
http://forum.xda-developers.com/showthread.php?t=832240&highlight=drivers
Read this also it will help
http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/
As for your problem im sorry i cant help you out but if you post in the Q&A section like your supposed to then im sure someone there can figure it out. Possibly IMPALER as he seems to be on alot.
Good Luck with finding something out.
Click to expand...
Click to collapse
I need x32 not x64...so I'm back at square one. Plus I did post in the right section in addition to this one. I got 41 views and no replies...that sucks right...
Try using Rom manager to re-flash clockwork?
Plan C: RUU your phone, and re-root and go from there...
There is no reason for him to reflash any recovery, as adb connectivity starts in recovery and drops when you pass it or reboot the phone and picks up from the rom itself (the adb communication interface is built into all versions of android)
Win7 32bit works fine with the 32bit ADB drivers, but just like the 64bit win7, it has hickups sometimes. That's your problem I am sure. Sometimes when you disconnect and reconnect a device (or it reboots) in windows 7 the drivers crash, and what win7 does as opposed to xp or vista, is sort of blacklisting the driver to stop it from crashing the rest of the windows system.
Ergo, you just need to reinstall the drivers you already have.. Have you tried that?
BTW, HTC Sync drivers are completely different than ADB drivers, and will cause conflicts. Did you install HTC Sync lately?
One last thing, you remember where you installed adb? Or rather your Android-sdk-Windows directory? From there it is in the usb_driver folder.
i.e. if you installed to the root of your drive, it would be in:
c:\android-sdk-windows\usb_driver\
The name of the file is android_winusb.inf
Well when you do, or either way, someone move this to the q-n-a section.
Problem solved.
"Gregory House 1, God 0" - Gregory House
B-Nice_88 said:
I need x32 not x64...so I'm back at square one. Plus I did post in the right section in addition to this one. I got 41 views and no replies...that sucks right...
Click to expand...
Click to collapse
Hows this going? Try pming carbon kang he had the same issue back in May it's happened to quite a few of us after using a different recovery and flashing this one rom. I know it sounds crazy and shouldn't be happening but it did. The thread that it was in got deleted probably by mistake.
What do those who know know about this particular liklihood. My gut tells me we will see this "MOD" sooner rather than later due to the ability to port from the TMOBILE version already in place. What are your thoughts gentlemen / ladies?
I hope so...Just need some devs to get skyrockets and this place should get busy. I just started getting nightlies on my atrix and I couldn't help but get a new phone.
Phoneguy589 said:
I hope so...Just need some devs to get skyrockets and this place should get busy. I just started getting nightlies on my atrix and I couldn't help but get a new phone.
Click to expand...
Click to collapse
Did the exact same thing, just had nightly #9 on the atrix when I decided to go buy this phone. Hopefully it wont be that hard to port the T-mobile version.
Did you root yet?
Of Course
I'm trying darklords script but it's stuck on waiting for phone. USB debug is enabled and unknown sources is enabled. Not sure why it's not starting.
Phoneguy589 said:
I'm trying darklords script but it's stuck on waiting for phone. USB debug is enabled and unknown sources is enabled. Not sure why it's not starting.
Click to expand...
Click to collapse
Did you install Samsung Kies for the USB drivers? That's been the most common problem.
You can always open the batch script in an editor, start running the commands one line at a time by hand and see where it's failing. (Just ignore the @files\ prefix)
For some reason it dropped the usb connection from the computer so I ran Kies and it reinstalled the drivers. After that, it rooted with no issues. Running my rooted apps I bought and all is running great.
My buddy was making a custom app and when i plug my nexus s running ics it recognizes the phone as a usb storage drive but it will not come up on his computer to test run the app. The only thing i can do is open the files of the phone to see whats inside. Can anyone help me with this problem?
I don't think we understand what exactly is happening. You'll have to explain it better.
basically the android sdk will not read my phone and it does not come up as one of the options.
I'm sorry but I'm not able to troubleshoot this with you with the info you provided.
Which phone do you have? What ROM? Which recovery version? Do you have proper drivers installed? Windows/Mac/Linux?
And what does your friend's app has to do with any of that and which app are you talking about?
I have a problem. I just got my Android a couple of days ago and I really badly want to root it. I've tried multiple different programs and with each one the problem I get is "Waiting for device" in the cmd/terminal (Tried on multiple platforms: Vista, Win7, Ubuntu). I've tried installing drivers too and still didn't work (maybe the wrong drivers?).
Yes I realize that I am a "noob", but I really need some help here.
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
azzledazzle said:
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
Click to expand...
Click to collapse
>Yes
>I think so, not positive.
> What do you mean?
bumpp someone help?
Well Redownload the drivers and see if that helps, You could try Hasoon2000's All In One Kit to help with this. http://forum.xda-developers.com/showthread.php?t=1604677
As for ADB, (Android Debug Bridge) you should have this already, You need it to get unlock the bootloader and flash superboot (root) http://forum.xda-developers.com/showthread.php?t=1583427
Be sure to check out those links and also look at my FAQ section http://forum.xda-developers.com/showpost.php?p=24884624&postcount=3
I have all the files that it says are necessary to unlock the bootloader. It's just when I type "fastboot oem get_identifier_token" it just sits there saying "waiting for device".
I've tried hansoon's all in one program as well and it didn't work either.
Well that means it cannot find your phone, So the issue lies with the drivers and/or the location from which the command prompt is opened..
Put all of the files into 1 folder called android or adb and move that 1 folder to the root of your C Drive..
This should make navigating easier. Also, In that folder should be adb.exe and fastboot.exe do you have these ?
I fixed this by just playing around with it a bit more. Thanks for the help, though.
infam0us me said:
I fixed this by just playing around with it a bit more. Thanks for the help, though.
Click to expand...
Click to collapse
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
morphication said:
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
Click to expand...
Click to collapse
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
infam0us me said:
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
Click to expand...
Click to collapse
ok. it was windows 8 not allowing unsigned drivers to install properly. note: not "not installing at all", but "not installing properly". meaning: htc drivers installed somehow, so I was able to see the device and copy files around, but it was not enough for flashing roms.
so I started this guide to disable driver signature:
https://www.youtube.com/watch?v=gmw86KplqmU
... but my laptop is a business laptop and this guide demands BitLocker key if hard drive is encrypted (mine is). I also have a windows 7 desktop machine. So I decided to go the easy and quick way of simply doing flashing on my desktop computer. Windows 7 worked like a charm. But I'm sure the guide above would've helped as well. If somebody tries that, please post results.
Hi, I have a Deco 77x (MediaTek MT6572) and I need to install drivers on my PC to flash a custom ROM.
The drivers are successfully installed but I can't install the last one: "MT65xx Android Phone". I tried reinstalling drivers, rebooting and disabling driver signature enforcing.
I have WinXP Sp3.
Also tried in Win10(Parallels Desktop on my MacBook Pro) with no success, some drivers are not detected in VM.
Is someone knows what can I do?
Thank you!
crik91 said:
Hi, I have a Deco 77x (MediaTek MT6572) and I need to install drivers on my PC to flash a custom ROM.
The drivers are successfully installed but I can't install the last one: "MT65xx Android Phone". I tried reinstalling drivers, rebooting and disabling driver signature enforcing.
I have WinXP Sp3.
Also tried in Win10(Parallels Desktop on my MacBook Pro) with no success, some drivers are not detected in VM.
Is someone knows what can I do?
Thank you!
Click to expand...
Click to collapse
You're having PC issues, find a PC forum.
This forum is for issues on android, not PC.
Sent from my SM-S903VL using Tapatalk
Re-tried with another one Windows10 x64 PC(not on VM) yesterday. Same issue. I don't think that it's a PC issue.
crik91 said:
Re-tried with another one Windows10 x64 PC(not on VM) yesterday. Same issue. I don't think that it's a PC issue.
Click to expand...
Click to collapse
Installing drivers on a PC is most definitely a PC thing and not an android thing.
As already stated, find a PC forum and figure out why your driver's won't install on your PC.
Sent from my SM-S903VL using Tapatalk
Drivers are installed in all my PCs(also Win10 in VM), I can't install the phone.. It's not possible to have same issues in 3 PCs with different OS.
crik91 said:
Drivers are installed in all my PCs(also Win10 in VM), I can't install the phone.. It's not possible to have same issues in 3 PCs with different OS.
Click to expand...
Click to collapse
Your issue is with getting the drivers installed on PC, correct?
This is not an issue with something you're doing to the phone itself, it's an issue with getting your PC'S to accept the drivers, that is not an "ANDROID" issue.
A PC forum will help you figure out why your PC's arent accepting the drivers and get them to install correctly.
This forum is for help with things you are doing to your actual android device, not for issues with the systems you are using to interface with your android device.
Sent from my SM-S903VL using Tapatalk
Ok, but this forum is full of users that have issues with drivers and full of other users that answered and helped to solve.
I do not think it is as bad if I ask here.
My question is for someone that can and wants to help me like in others posts.
Thanks anyway.
crik91 said:
Ok, but this forum is full of users that have issues with drivers and full of other users that answered and helped to solve.
I do not think it is as bad if I ask here.
My question is for someone that can and wants to help me like in others posts.
Thanks anyway.
Click to expand...
Click to collapse
Yes, I know driver questions have been asked and answered here before.
My point is you would get better and quicker solution in a PC forum, have it your way though, if you'd gone to a PC forum when I told you, you'd probably already have the solution.
I'm sure you'd rather have a solution as soon as possible, correct? So why not go to where the specialty is PC related issues, the kind of place where they deal with this kind of issue a lot more than it is dealt with here.
Am I making any sense yet? Or are you just refusing to understand?
Sent from my SM-S903VL using Tapatalk