Go Back   Android Forums > Android Phones > Virgin Mobile Venture > Venture - All Things Root

Like Tree4Likes
  • 1 Post By Dracable
  • 1 Post By AmpJack
  • 1 Post By Dracable
  • 1 Post By iowabowtech

test: Reply
 
LinkBack Thread Tools
Old November 4th, 2012, 09:06 AM   #1 (permalink)
New Member
Thread Author (OP)
 
Join Date: Aug 2012
Posts: 3
 
Device(s): VM Venture
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default Having an ADB Issue Device Not Found

Been working at this all morning.
Can't for the life of me get ADB to find my phone.
I installed PDANet, selected Other when prompted asking who made my phone for the drivers.
My phone is listed in Device Manager as 'Android Phone>Android ADB Interface'.
I've tried restarting phone and computer, with and without PDANet running on my phone and computer (It doesn't need to be running though, right?)
Running Windows 7 Ultimate 32-bit.
If any more info is needed, just let me know.

Thanks for any help.

Advertisements
AmpJack is offline  
Reply With Quote
sponsored links
Old November 4th, 2012, 09:19 AM   #2 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,435
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,366
Thanked 7,551 Times in 3,966 Posts
Default

I don't own this phone but after reading a few threads, it seems like the pdanet route is the best option for drivers. Also, generally when it shows adb interface, that means its ready to go. So, what exactly are you doing to test? adb devices command I assume? Are you running it from the platform-tools directory?
iowabowtech is offline  
Reply With Quote
Old November 4th, 2012, 10:22 AM   #3 (permalink)
AF Contributor
 
Join Date: Oct 2012
Location: Humboldt County, CA
Gender: Male
Posts: 614
 
Device(s): Virgin Mobile Alcatel Venture (x3)
Carrier: Virgin Mobile

Thanks: 32
Thanked 107 Times in 84 Posts
Default

if it is showing in your device manager, adb should be successfully installed. did you follow the link to download the android sdk as well? if so, you should be set. and no, pdanet does not need to be running for adb to work. what exactly are you trying to do that makes u think that adb is not working? are you trying to flash cwm recovery? if so, what steps are you taking, and what exactly leads you to believe adb isnt functioning? hang tight buddy, we'll get u up and running!
varenHjames likes this.
Dracable is offline  
Reply With Quote
Old November 4th, 2012, 10:24 AM   #4 (permalink)
New Member
Thread Author (OP)
 
Join Date: Aug 2012
Posts: 3
 
Device(s): VM Venture
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Yeah, I had already downloaded PdaNet. I'd get into platform-tools, run adb.exe then adb devices.
I was able to run a wireless ADB app and flash recovery through that.
For anyone having trouble with the normal method, you can search ADB Wireless and download any of the apps for it. Open app, click a button to start then go to ADB and type "adb connect xxx.xxx.x.x:xxxx" (ip and port info will be shown on app.)

Thanks for the quick replies, guys.
varenHjames likes this.
AmpJack is offline  
Last edited by AmpJack; November 4th, 2012 at 10:27 AM.
Reply With Quote
Old November 4th, 2012, 11:14 AM   #5 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,435
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,366
Thanked 7,551 Times in 3,966 Posts
Default

Quote:
Originally Posted by A***ack View Post
I'd get into platform-tools, run adb.exe then adb devices.
Unless I'm misunderstanding your intent, you don't run adb.exe. I'm assuming we are talking about the one housed within the platform-tools folder along with fastboot for that matter. Instead, you want to use your command prompt on the PC and navigate to that directory, then run the adb devices command. There is no running of an .exe package. So assuming you installed the sdk on the root of the c drive as most guides tell folks to do, you would then plug in the phone, make sure usb debugging is selected on the phone, open a prompt on the pc and do this:

cd c:\android-sdk-windows\platform-tools

then...

adb devices

And that should output the s/n of your device. If so, you're in.
iowabowtech is offline  
Reply With Quote
Old November 4th, 2012, 12:02 PM   #6 (permalink)
AF Contributor
 
Join Date: Oct 2012
Location: Humboldt County, CA
Gender: Male
Posts: 614
 
Device(s): Virgin Mobile Alcatel Venture (x3)
Carrier: Virgin Mobile

Thanks: 32
Thanked 107 Times in 84 Posts
Default

also, just a handy little tip for users of vista and above...
instead of having to open a command prompt and manually navigate to the platform-tools folder, you can just browse to the folder in windows, hold shift, and right click in any empty part of the folder window, and it will bring up an option to run a command prompt from that location. so when command prompt opens, it will automatically be in the platform-tools directory. just a little tip to make ur lives a tad easier!

...The More You Know...
iowabowtech likes this.
Dracable is offline  
Reply With Quote
The Following User Says Thank You to Dracable For This Useful Post:
iowabowtech (November 4th, 2012)
Old November 4th, 2012, 12:17 PM   #7 (permalink)
root@android:/ #
 
iowabowtech's Avatar
 
Join Date: May 2010
Location: Iowa|USA
Posts: 10,435
 
Device(s): LG G2
Carrier: VZW

Thanks: 5,366
Thanked 7,551 Times in 3,966 Posts
Default

Cool tip. Even better yet, set up an environmental variable. Then you can adb/fast boot globally with no need to goto platform-tools at all. That can always be done but first we need to get past this issue of no connectivity. I guess you found a workaround anyway but its always nice to get adb up and running to know its there if needed. Cuz you may not always have a booting phone to start up a wireless app.
varenHjames likes this.
iowabowtech is offline  
Reply With Quote
The Following User Says Thank You to iowabowtech For This Useful Post:
varenHjames (November 4th, 2012)
Old November 6th, 2012, 08:38 PM   #8 (permalink)
New Member
Thread Author (OP)
 
Join Date: Aug 2012
Posts: 3
 
Device(s): VM Venture
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by iowabowtech View Post
Unless I'm misunderstanding your intent, you don't run adb.exe. I'm assuming we are talking about the one housed within the platform-tools folder along with fastboot for that matter. Instead, you want to use your command prompt on the PC and navigate to that directory, then run the adb devices command. There is no running of an .exe package. So assuming you installed the sdk on the root of the c drive as most guides tell folks to do, you would then plug in the phone, make sure usb debugging is selected on the phone, open a prompt on the pc and do this:

cd c:\android-sdk-windows\platform-tools

then...

adb devices

And that should output the s/n of your device. If so, you're in.
Did not mean that, adb.exe running in command prompt. XP
It was all set, I've gone a few rounds. HD2 and what-not.
I think it was a port issue not allowing me to connect the phone, but after I hooked it up through the router it went through fine.
Gotta' reinstall Windows 7 probably. Firewall is all funked up, Microsoft fixes do no good. Ah well though.
AmpJack is offline  
Last edited by AmpJack; November 6th, 2012 at 08:41 PM.
Reply With Quote
Reply
Tags
adb, alcatel, pcd, venture, virgin


Go Back   Android Forums > Android Phones > Virgin Mobile Venture > Venture - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 08:41 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.