BH_MAN

For those Having Trouble with adb in Linux, Replace the current adb file in your sdk/tools folder ( or where every the file location might be ) with the File I have Linked... This will still work with all other phone's that you may have...

Working ADB replacement File For the Behold 2 here > adb.gz

Once Downloaded, Extract the File and do the Following Directions above, then Repair Permission on the adb file with command below \/
Chmod a+x ( adb file location )

Next we Need to add the 51-android.rules for adb to work correctly.
51-android.rules Download > 51-android.rules

Special thanks to barakinflorida for passing me this File's for everyone to use, I didn't have this issue with adb to begin with, but Barak did & knew how to fix it for you guys...

__________________
Twitter http://twitter.com/Eugene_373 Show thanks?Just send me a PM with a thanks you...
IF you want to buy me a Beer, Click on the Text.*edit* All Donations Goes to Baby Toys now

Last edited by BH_MAN; April 7th, 2010 at 08:26 PM.

chadmd23

Can you post your rules.d file for us also? Just the text and file name would help out, so we can copy and paste.

Thanks!

__________________
Please take a second to search for your answer, and keep the forums clean of repeat postings. Thanks!

BH_MAN

sure no problem.. give me a minute to boot into linux to grab it for everyone... forgot about that.

*Edit*
I'm bad about explaining stuff, so Barak is making a how-to regarding the Rules.d file right now.... I'll Post it shortly for everyone.

Please send a thank you to barak via twitter if you get time...

Last edited by BH_MAN; April 7th, 2010 at 08:04 PM.

megabiteg

Thanks a lot BH_MAN, I've been looking all over for this, and reading everything and anything I can find...

Once this is fixed and done, can someone explain why is that ADB wasn't recognizing the phone? I would like to know for background knowledge.

THANKS!

__________________
----
"Perfection is my life goal, excellence will be tolerated."

chadmd23

Here is a shot at what I think is happening. The UDEV (device manager) is not looking in the right place for your phone. It looks at the rules.d file so it has guidance as to where to look for the device, but its not telling it the correct location.

BH_MAN

Okay I updated the OP & link

chadmd23

No dice for me.

BH_MAN

Well that Sucks man.... I posted what works for me & Barak... is the export path setup correct?

chadmd23

Not sure what you mean by export path. I'm going to change the rules file name to a few other things and try again.

megabiteg

Chadmd, this worked for me too, let me go over what I did.

After downloading the files, I moved the adb to the (in my pc is like this) ~/android/tools/ folder and ran the chmod a+rwx adb command.

After this, I took the rules file and I moved it to the /etc/udev/rules.d/ folder (logged as root). After doing this, I ran the following commands:

su [then placed the password]
chmod a+x 51-android.rules
chown root:root 51-android.rules

Once done, I restarted the PC and its working 100%, I ran the lsusb command to confirm the connection of the device and then a ./adb devices an I got positive return!

Thanks Barak and BH_MAN for the extra hand. I think that the only place I was failing was the permissions on the rules file, I had the rules file just like barak after my last research.

Last edited by megabiteg; April 7th, 2010 at 11:53 PM.

chadmd23

Got it!! Thanks guys. Not that familiar with su usage, thats where my problem was.

Now to try Proxoid.

UPDATE: It works, just not as easy to use as pdanet.

Last edited by chadmd23; April 7th, 2010 at 11:53 PM.

khunny7

Thank you so much. Thank you thank you thank you!

aequitas3

@megabiteg....im geting stuck on the su... keep getting su: authentication faiure... could you help explain what this is and/or how to fix? sorry, n00b to ubuntu world. runnin 9.04 if that helps any...

megabiteg

If you have never used the "su" command before chances you have a generated root password that comes with the installation. This is the same thing that happens with a new Windows install that you don't get access to the Administrator user.

To fix this do the following:

sudo passwd
(authenticate sudo; this is the password you put all the time when you run the sudo command)
(enter and confirm the new password for root)

After this you should be all set to elevate yourself to root without issues using the new password you assigned after the sudo authentication.

let me know if you need additional help.