Hi guys,
just wanted to share udev rules for our P8000 for anyone interested in using ADB and Fastboot with Linux
Code:
#Elephone P8000 ADB
SUBSYSTEM=="usb", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="201d", MODE="0600", OWNER="<your user>"
#Elephone P8000 Fastboot
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c01", MODE="0600", OWNER="<your user>"
Any appends would be welcome
To use this you would need to create a File in
Code:
/etc/udev/rules.d
like
Code:
51-android.rules
After this you have to reload udev daemon
Code:
sudo udevadm control --reload
Now you can connect your phone to your computer
If this doesn't work, Output of lsusb when connected via fastboot and/or ADB would be usefull
Hope this helps some people
I assume should be replaced by the Ubuntu username?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Sorry for the late answer
Yes you are right but I assume you have already tried this
If you have further problems, just ask
Related
[Resolved]
Hi, I try to root my LG Eve with Wiki, I follow all steps but when I lauch "adb shell", the terminal returns me "error: insufficient permissions for device".
The step Module Test -> Stability Test -> Enable Root Permission seems not working...
Any idea? Thanks
PS Sorry for my english...
Click to expand...
Click to collapse
[Resolved]
i Have the same problem!
vinzqc said:
[Resolved]
[Resolved]
Click to expand...
Click to collapse
Maybe the resolution could be shared?
The adb server needs to start as root to get full access to the USB device.
Code:
adb kill-server
sudo adb start-server
adb devices
adb shell
did you check your udev rules? if you set this up you don't need to run adb server as root.
http://developer.android.com/guide/developing/device.html
Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
Use this format to add each vendor to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.
be sure to change group to "users" or your group name (type id -a)!
adb do not need as root in my phone with official rom, but it is needed in cm72
Hi, i'm trying to live test my app created with eclipse on my HTC Desire but i cant get it working!!
I'm using Eclipse Helios under Ubuntu 10.10 32bits
What i did :
- this trick http://developer.android.com/guide/developing/device.html but with no luck...
- set Debuggable to true in the AndroidManifest.xml
- USB debug is activated on my phone
- Tried to launch eclipse with root access
Also tried with both
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
Click to expand...
Click to collapse
as well as 99-android.rules and 90-android.rules
All i have with adb devices is ???????????? (same in the DDMS window in eclipse)
btw, i'm using a different usb cable (from an external hard drive) because i lost the old one. But i assume that my problem has nothing to do with that change.
Thank you for your time
OK, resolved using
sudo adb kill-server
sudo adb start-server
adb devices
Click to expand...
Click to collapse
sorry for asking before searching...
So I have had a hell of a time getting adb to recognize my device on the latest Ubuntu 11.04
I have looked at numerous tutorials and scoured through pages and pages but no matter what I do, I can't get adb to recognize my device.
If anyone has any experience setting this up on 11.04 please let me know, thanks.
i didnt have any problems setting mine up.
i didnt add my usb devices to my udev rules yet, so i just run
Code:
sudo adb blahblahblah
either be in your platform-tools directory or copy adb into /usr/bin
Code:
sudo cp adb /usr/bin/
Pirateghost said:
i didnt have any problems setting mine up.
i didnt add my usb devices to my udev rules yet, so i just run
Code:
sudo adb blahblahblah
either be in your platform-tools directory or copy adb into /usr/bin
Code:
sudo cp adb /usr/bin/
Click to expand...
Click to collapse
Thank you I got it working now. I had forgot to enable usb devices on my virtualbox (created a new one).
I feel stupid but thank you for your reply!
you dont get
???????????????
listed in the device when you type adb devices?
This link has all the system IDs on it. Just add the one for HTC where it says to.
Sent from a Western Union telegram.
I had followed all of the instructions previously and it would have worked had I enabled usb devices in VirtualBox originally. Since usb was not enabled..that is why it was showing nothing when I typed "ADB Devices".
All is good now. I am back to compiling.
Why are you using it through Virtualbox, when you can easily dual boot?
I ask because I dual boot Win7 and Ubuntu. I upgraded from 10.10 to 11.04 and haven't had any issues with adb. I used to with 10.10 until I realized I forgot to set udev rules.
the Android instructions are a little dated - don't use the SYSFS attribute in udev rules, but use ATTRS.
For example:
Code:
[email protected]:/etc/udev/rules.d$ cat 51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
And don't forget to restart udev. Unplug the device, do the command below and then plug back in. HTH.
Code:
sudo /etc/init.d/udev restart
Ive been trying to flash CWM for 2 days with no luck so finally i am asking for help.
first off i bought a VZW GNEX (toro) w/ 4.2.2 from a buddy for $20
ive tried the nexus toolkit and tried flashing manually with fastboot/adb
i can unlock bootloader no problem but everytime i try to flash CWM, toolkit or manually, it just stays on
adb devices will show my device but fastboot devices wont
i have the .img in the correct folder of platform-tools
im running linux mint 13 and id prefer to do it manually just cause im not a big fan of 1-click methods
Do I need to use the Universal Naked drivers?
any advice would be greatly appreciated and thanx in advance
Drivers do not apply in this situation.
if your device is in FASTBOOT mode, then ADB should not see it at all. Fastboot and ADB are 2 completely different modes.
if you can unlock the bootloader, then your fastboot should be working properly, since thats what is required to unlock.
boot to fastboot and give the output of
fastboot devices
Pirateghost said:
boot to fastboot and give the output of
fastboot devices
Click to expand...
Click to collapse
no output at all i hit enter and it goes right back to the command line
[email protected] ~/droid_****/android-sdk-linux/platform-tools $ fastboot devices
[email protected] ~/droid_****/android-sdk-linux/platform-tools $
DowneyJM said:
no output at all i hit enter and it goes right back to the command line
[email protected] ~/droid_****/android-sdk-linux/platform-tools $ fastboot devices
[email protected] ~/droid_****/android-sdk-linux/platform-tools $
Click to expand...
Click to collapse
do you have fastboot in your path and all is configured properly?
if you dont have your udev rules and paths set straight, it can cause issues.
try sudo ./fastboot devices
Pirateghost said:
do you have fastboot in your path and all is configured properly?
if you dont have your udev rules and paths set straight, it can cause issues.
try sudo ./fastboot devices
Click to expand...
Click to collapse
no difference with sudo
i followed a post somewhere that had me create a file /etc/udev/rules.d/51-android.rules
and add the following line to it
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
lemme guess i gotta add my device id ?????
is this my problem?
Curious to know how you unlocked the boot loader if fast boot really doesn't see the device. Can you fastboot OEM lock it back?
Sent from my Galaxy Nexus
Code:
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="username"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="username"
Change username to your own normal user, reconnect the device. Does Mint use systemd already? Then check 'journalctl -b -f' and see if its recognising the device, also check 'lsusb'.
I believe fastboot is in his path because he doesn't get a 404 and also, if he just 'chmod +x fastboot' and try to run it from any location, he would have to './fastboot command partition filename'.
Sent from my Nexus
Pirateghost said:
Curious to know how you unlocked the boot loader if fast boot really doesn't see the device. Can you fastboot OEM lock it back?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i was able to manually lock and unlock bootloader
bk201doesntexist said:
Code:
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="username"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="username"
Change username to your own normal user, reconnect the device. Does Mint use systemd already? Then check 'journalctl -b -f' and see if its recognising the device, also check 'lsusb'.
I believe fastboot is in his path because he doesn't get a 404 and also, if he just 'chmod +x fastboot' and try to run it from any location, he would have to './fastboot command partition filename'.
Sent from my Nexus
Click to expand...
Click to collapse
no systemd for mint but lsusb shows device connected
after edititng 51-android.rules problem was solved!
thanx to both of you for taking the time to help me get squared away
that is the beauty of an open source community
what ROM do you guise recommend?
DowneyJM said:
i was able to manually lock and unlock bootloader
no systemd for mint but lsusb shows device connected
after edititng 51-android.rules problem was solved!
thanx to both of you for taking the time to help me get squared away
that is the beauty of an open source community
what ROM do you guise recommend?
Click to expand...
Click to collapse
Plenty of roms here, you choose your own fate
This thread is solved, please report it to the mod team for closing, thanks.
edit: reported for closing
Thread closed
Hi friends,
a short tutorial for rooting Ventos 10.1 from simple user Linux Ubuntu, when ADB doesn't recognise the device using Root_with_Restore_by_Bin4ry_v33 from this thread.
Disclaimer: The following rooting guides take software from third-party sources and are not products of danjde. I cannot be held responsible for any effects on your device resulting from this rooting guides. Please attempt only after reading through and understanding the guide(s) and proceed with caution.
ATTENTION: TABLET BATTERY MUST BE CHARGED!!
ALL FROM LINUX CONSOLE/TERMINAL WITHOUT EXTERNAL APPLICATIONS
1) edit from super user editor and add the correct USB Ids to /var/lib/usbutils/usb.ids:
2207 RocketChip
now lsusb should show the device properly
lsusb
Bus 001 Device 012: ID 2207:0010 RocketChip
2) add udev rule in /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0666", GROUP="plugdev"
3) restart udev service
service udev reload
4) optionally add vendor id in ~/.android/adb_usb.ini or in the same adb location
0x2207
5) extract the content of Root_with_Restore_by_Bin4ry_v33 and give executions permission to all fro semplicity (compessing whith zip have lost attributes)
chmod -R 755 "extracted-folder"
6) cd into the utility "Root_with_Restore_by_Bin4ry" directory
cd stuff
7) restart adb server
./adb kill-server
./adb start-server
8) connect Ventos and enable usb debugging.
9) now adb devices shows the device.
./adb devices
224DDD88E8722FA848300A20B9F8XXXX device
10) run as normal user
./RunMe.sh
[IMPORTANT: if you obtain on 64bit linux machine: "/stuff/adb: error while loading shared libraries: libncurses.so.5..."
install lib32ncurses5: apt-get install lib32ncurses5 and try again]
11) select normal mode
12) wait until 5 minus
finish!
tested :good:
Dear Danjde,
I habe a Trekstor Surftab Ventos 10.1 that I would like To root.
It appears, however, hat there exist At least 2 Version oft the tablet.
In Android settings it is called ST10216-2A.
Can you confirm your Version?
Also, is it possible To root the device fron a local shell via the same commands AS in the *.SH file?
Thank you so much!
Andreas
Hi der.einstein,
I confirm that two are the ventos 10.1 versions,
mine is the second, and from my research the method shown applies to both models.
For the second question the answer is: no
ciao!