Very nice work thank you for sharing.
Printable View
Very nice work thank you for sharing.
EXACTLY WHAT I WANT TO KNOW!! I was able to get to the point where it showed my device information, and I can get the KDZ Updater to open with WINE, but "PHONE NOT FOUND"....
I've read through the GOOGLEs but never really found any way of doing this...
I suppose reading the man for adb could work, but it doesn't mention SPECIFICALLY kdz files..
Have you any update on this?
The KEY for me, is getting the phone in a safe state to push the update. The KDZ Updater puts the device into emergency mode...but I wouldn't know how it's done from adb.
Thank you! Worked for me :D Now I can fix my phone.
At first the installation didn't work for me, then I found this which suggests installing ia32-libs...
Starting with Ubuntu Quantal, you can install the packages android-tools-adb and android-tools-fastboot.
This is interesting because you also get a native amd64 package.
Thanks for the tutorial. I actually just wimped out and didn't make the udev rule. Just go to the platform-tools folder in a terminal and runor whichever adb command you want. Works better for me because I'm just doing a one time thing on a borrowed device.Code:./adb shell
can't get it working with htc vivid
here is my info:
and command udevadm test --action=SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="0bb4",ENV{ID_MODEL_ID}=="0ff0" , MODE="0666" gives me an error:Quote:
udevadm info -q all --path /sys/bus/usb/devices/2-3P: /devices/pci0000:00/0000:00:1d.7/usb2/2-3
N: bus/usb/002/023
E: BUSNUM=002
E: DEVNAME=/dev/bus/usb/002/023
E: DEVNUM=023
E: DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-3
E: DEVTYPE=usb_device
E: DRIVER=usb
E: ID_BUS=usb
E: ID_MODEL=Android_1.0
E: ID_MODEL_ENC=Android\x201.0
E: ID_MODEL_ID=0ff0
E: ID_REVISION=0100
E: ID_SERIAL=htc__Inc_Android_1.0_HT1ASVJ25491
E: ID_SERIAL_SHORT=HT1ASVJ25491
E: ID_USB_INTERFACES=:ff4203:
E: ID_VENDOR=htc__Inc
E: ID_VENDOR_ENC=htc\x2c\x20Inc
E: ID_VENDOR_ID=0bb4
E: MAJOR=189
E: MINOR=150
E: PRODUCT=bb4/ff0/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: UDEV_LOG=3
E: USEC_INITIALIZED=2423343578
unable to open device '/sysENV{ID_VENDOR_ID}==0bb4,ENV{ID_MODEL_ID}==0ff0, '
please, help me with udev rule!
Looks easy, but I always receive an error - device not found
My Problem is, the device has NO NAME, if I send an lsusb command, I only receive for my android-device the line:
Bus 001 Device 016: ID 2207:290a
and nothing more ... but every time I need to connect new, the Device-Number grows higher (first it was 005 ... now 016 ...)
How can I connect this device with NO NAME ???
The problem is, as device-name there is nothing, but can you help me, how I can connect nothing to use nothing with adb ... ??? :lolflag:
But I can not laugh about it, because this fu... android-tablet with no name cannot be found in adb, not with OS Ubuntu, nor under Windows :-(
Only with the RKBatchtool under Windows I can see it and I can flash the original Rom :-(
but I want to root it ............ can anybody help me with my EasyPix EasyPad EP750 ... its everything else than easy :-(
Don't know if my udev-rules work: SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="2207", ENV{ID_MODEL_ID}=="290a", MODE="0666"
I followed this process on my Ubuntu 12.04 LTS box, and when I try to run adb, I get the old "no such file or directory". Permissions appear OK on adb (-rwxrwxr-x). What gives?