Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[HELP] ADB cannot find my ville C2!

OP xQubee5o3

17th June 2014, 05:14 PM   |  #1  
xQubee5o3's Avatar
OP Senior Member
Flag Duisburg
Thanks Meter: 76
 
133 posts
Join Date:Joined: Sep 2013
More
Hey guys.

So far, I am working on Ubuntu 13.10 to install Ubuntu touch on my device.
Guys, this is my problem, what is raging me, because it's just a question of drivers -.-

Code:
hal5000@HAL-5000:~/development/android-sdk-linux/platform-tools$ adb devices
List of devices attached 
SH265W------	offline
I cannot find my device.
Can anyone help me to fix this?
In bootloader, I cannot do any adb commands, because my terminal is always showing me this:

Code:
hal5000@HAL-5000:~$ adb kill-server
hal5000@HAL-5000:~$ adb start-server
* daemon not running. starting it now on port 5037 *

* daemon started successfully *
hal5000@HAL-5000:~$ 
hal5000@HAL-5000:~$ cd ~/development/android-sdk-linux/platform-tools
hal5000@HAL-5000:~/development/android-sdk-linux/platform-tools$ ubuntu-device-flash --channel=devel --bootstrap
2014/06/17 17:10:48 Expecting the device to be in the bootloader... waiting
I have updatet my SDK and my adb is full-updated.
Please help me as fast as you can.. (I'm a little bit noobish on ubuntu)

Greetz
Mii La Bee <3
20th June 2014, 11:18 PM   |  #2  
xQubee5o3's Avatar
OP Senior Member
Flag Duisburg
Thanks Meter: 76
 
133 posts
Join Date:Joined: Sep 2013
More
Push..

Sent from my Bee-Phone using Honey. Greetz! Mii La Bee. <3
22nd June 2014, 09:38 AM   |  #3  
Junior Member
Thanks Meter: 3
 
10 posts
Join Date:Joined: Mar 2010
Try running adb under root:
Code:
sudo adb kill-server
adb kill-server
sudo adb start-server
AND/OR:

Run:
Code:
lsusb
Output example:
Code:
Bus 002 Device 103: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Create new rules file (/lib/udev/rules.d/10-adb.rules), and add this rule to it (edit it with the correct information):
Code:
# ADB
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="your_username"
Then restart udev (udevadm control --reload-rules) or reboot your computer.
Last edited by Black SpideR; 22nd June 2014 at 09:43 AM.
The Following User Says Thank You to Black SpideR For This Useful Post: [ View ]
30th June 2014, 12:29 AM   |  #4  
xQubee5o3's Avatar
OP Senior Member
Flag Duisburg
Thanks Meter: 76
 
133 posts
Join Date:Joined: Sep 2013
More
Quote:
Originally Posted by Black SpideR

Try running adb under root:

Code:
sudo adb kill-server
adb kill-server
sudo adb start-server
AND/OR:

Run:
Code:
lsusb
Output example:
Code:
Bus 002 Device 103: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Create new rules file (/lib/udev/rules.d/10-adb.rules), and add this rule to it (edit it with the correct information):
Code:
# ADB
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="your_username"
Then restart udev (udevadm control --reload-rules) or reboot your computer.

Thanks.
Will try it soon.. I punched my PC.. so ... xD yea we have to wait..

Sent from my Bee-Phone using Honey. Greetz! Mii La Bee. <3
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes