Related
OK, I truly believe I have done my due diligence, but I have not been able to find anything solid that can help me get beyond the problem I'm having. The irony is that I first tried this on my WinXP box at work and could not get beyond the < waiting for device > problem, so I gave up and figured I would have no problem if I patiently waited to go home and try this in linux.
So here's everything I've done so far. As noted in the topic, I run the amd64 version of Ubuntu 11.04. I installed the Andoid SDK linux x86 version (there was no option for an amd64 version). I ran the tool/android client to download the platform-tools, so I got adb. With the phone running normally, I can connect it to my laptop and run "./adb devices" and I get back:
Code:
List of devices attached
43423541314354394D58 device
so that's working. When I run lsusb while the phone is running normally, I see
Code:
Bus 001 Device 020: ID 0fce:215b Sony Ericsson Mobile Communications AB
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue. When I run lsusb in this mode, I get:
Code:
Bus 001 Device 022: ID 0fce:0dde Sony Ericsson Mobile Communications AB
As a result, I set the contents of my /etc/udev/rules.d/51-android.rules to:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="215b", MODE="0666", OWNER="procyon"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0dde", MODE="0666", OWNER="procyon"
and just to make sure my file permissions are ok (since that seems to bite people in the behind a lot), my rule is
Code:
-rwxr-xr-x 1 root root 197 2011-08-11 01:24 /etc/udev/rules.d/51-android.rules
So, with my udev rules reloaded, I attempt a "sudo ./fastboot boot recoveryPLAY.img" and all I get is the unfortunate
Code:
< waiting for device >
I've done just everything I could thing of, have read several (literally dozens) of tutorials, forums posts, and all manner of Google searches, but nothing seems to help me. Some areas where I think I might be having a problem:
a) Obviously, I'm running the 32 bit version of the sdk instead of the 64 bit version. Could that be an issue here?
b) I've seen lots of posts that disagree on whether the rules file should start with a 50 or a 51. Does that matter?
c) Do I need anything else from the Android SDK other than the platform tools? I don't have that directory in my path, but I'm running everything from inside that directory, and I'm running it with sudo.
I think I've provided all the information that I can. Thanks in advance for any help or any light that anyone can shed.
ProcyonSJJ said:
OK, I truly believe I have done my due diligence, but I have not been able to find anything solid that can help me get beyond the problem I'm having. The irony is that I first tried this on my WinXP box at work and could not get beyond the < waiting for device > problem, so I gave up and figured I would have no problem if I patiently waited to go home and try this in linux.
So here's everything I've done so far. As noted in the topic, I run the amd64 version of Ubuntu 11.04. I installed the Andoid SDK linux x86 version (there was no option for an amd64 version). I ran the tool/android client to download the platform-tools, so I got adb. With the phone running normally, I can connect it to my laptop and run "./adb devices" and I get back:
Code:
List of devices attached
43423541314354394D58 device
so that's working. When I run lsusb while the phone is running normally, I see
Code:
Bus 001 Device 020: ID 0fce:215b Sony Ericsson Mobile Communications AB
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue. When I run lsusb in this mode, I get:
Code:
Bus 001 Device 022: ID 0fce:0dde Sony Ericsson Mobile Communications AB
As a result, I set the contents of my /etc/udev/rules.d/51-android.rules to:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="215b", MODE="0666", OWNER="procyon"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0dde", MODE="0666", OWNER="procyon"
and just to make sure my file permissions are ok (since that seems to bite people in the behind a lot), my rule is
Code:
-rwxr-xr-x 1 root root 197 2011-08-11 01:24 /etc/udev/rules.d/51-android.rules
So, with my udev rules reloaded, I attempt a "sudo ./fastboot boot recoveryPLAY.img" and all I get is the unfortunate
Code:
< waiting for device >
I've done just everything I could thing of, have read several (literally dozens) of tutorials, forums posts, and all manner of Google searches, but nothing seems to help me. Some areas where I think I might be having a problem:
a) Obviously, I'm running the 32 bit version of the sdk instead of the 64 bit version. Could that be an issue here?
b) I've seen lots of posts that disagree on whether the rules file should start with a 50 or a 51. Does that matter?
c) Do I need anything else from the Android SDK other than the platform tools? I don't have that directory in my path, but I'm running everything from inside that directory, and I'm running it with sudo.
I think I've provided all the information that I can. Thanks in advance for any help or any light that anyone can shed.
Click to expand...
Click to collapse
I rooted mine last night and I figured it out. Turn your phone completely off first. Unplug everything from the computer. Then hold the "search" button or the magnifying glass while you plug the cable into the phone. There should be a solid blue LED light color at the top of the phone. Then it should work!
There's no 64-bit version of the Android SDK. I think it may have to do with fastboot's binary.
Cubsfan3493 said:
I rooted mine last night and I figured it out. Turn your phone completely off first. Unplug everything from the computer. Then hold the "search" button or the magnifying glass while you plug the cable into the phone. There should be a solid blue LED light color at the top of the phone. Then it should work!
Click to expand...
Click to collapse
Did you not read:
Procyon said:
Then I power off the phone, disconnect it, hold down the search button, and reconnect it. The power LED turns blue.
Click to expand...
Click to collapse
@Logseman, where is the best place to obtain a good fastboot binary for linux besides the HTC distribution page?
Add -i 0x0fce to the actual fastboot command line too... I had the same problem as you
Thank you so much Blagus, that was exactly what I was missing. I was trying to follow the "Easy Way" method of rooting, as it seemed to be a method in which I would not need to bother ash or mills. Now that you've gotten me over this hurdle, I've come to realize that the "Easy Way" only works if you unlocked the bootloader first, so it appears that I must pm ash or mills anyway? Or is it recommended that I simply wait and be patient until they sort out whatever is needed to provide everyone with a single solution? Thanks again.
I don't get to see this in my R800i. I've put the fastboot binary (from HTC) in platform-tools and this folder in my path. Running "fastboot -i 0x0fce devices" simply returns me the fastboot manual.
Anybody get adb shell working on mac in terminal? Device doesn't even show up for me
Same issue here....
i got it to be recognized on my windows computer, but when i pull packages.xml nothing shows up anywhere.
No issues here; ensure developer/USB debugging is turned on and you are using a newer platform tools from Google.
You should be on platform tools Rev 9 or higher.
(If you downloaded the SDK go to the directory in shell/terminal on your mac, cd tools, then run ./android
This will let you do GUI based updates to the tools
In case you never had the SDK - I have posted my working Mac ADB and fastboot's here.
I have the same issue. I don't get it to be recognized when using ./adb usb or ./adb devices.
OS : Mac os X Lion 10.7.2
has anyone figured this out?
as far as I know I am running the latest SDK... but I will double check.
frustrating.
has anyone tried connected via Parallels?
UPDATE - just confirmed my SDK is at v15, so that can't be the issue.
Also - NPS_CA, your abd didn't work any better than mine - still not showing up.
make sure easy tether isn't installed on mac
So I am a bit done with just flashing other roms to my kaiser and also want to develop some apps and want to experiment with making my own roms, but initially just porting roms from other devices like the HTC wildfire. But I am not able to use debugging:
So this is what I have done I have installed the android sdk and also installed the ADT plugin for eclipse. Then I have compied the android-sdk file to the root of my c drive so it is easier to use the command line interface with this file. I then run the following commands in the cmd, as admin:
adb kill-server
adb start-server
adb devices
And here is where the **** just hits the fans I am unable to see my device in the list of devices. While my device is recognized by the computer as ADB Interface > HTC Dream Composite ADB Interface in the device manager section. (But I must note that when I click on the device it is noted: "Device cannot start. (code 10)" ) Also when I double click on the device in the regular computer windows (where all your hd's are showed) the file system of the device is empty!
So does anyone have any advice?
Have you test it from a live usb or CD GNU/Linux like Ubuntu?
Nope, I hoped that it would work in Windows, but I will try it in Linux if that would solve it.l But can you see anything that i am doing wrong or is it just Windows
I always have problems with USB management on Windows, all versions...with all my computers. Linux kernel seems to be better, imho, for USB.
I wanted to post this in case other people had the same problem as me. I have a Verizon LG Vortex and run Ubuntu 11.04 After installing the Android SDK and following The Lazyman's installation Guide to ADB for Ubuntu 10.10 I found that when I did ./adb devices I ended up with an empty list. After beating my head against the wall for several hours, I discovered that the usb mode needed to be changed to Modem Mode. To Do this I tapped the notification message that said my USB was connected and the selected "modem mode" from the drop-down. After that adb saw my device and I was able to send commands to it.
Hi,
I'm trying to unlock bootloader on my GNex but unfortunately, when i reboot it in fastmode (through adb reboot-bootloader or pressing VOL- , VOL+ and POWER), the device do nothing: It shows an android with "the chest open", in the top of the it shows "START" but any button works and when i try fastboot devices command, i have no response. i try to see if there is any device connected through lsusb, but the device doesn't appears.
It seems to be stuck and the only way to reboot in normal mode is removing the battery.
Anyone could help me?
Thanks,
xekin
More info about:
This is what is shown in fastboot mode:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro
HW VERSION - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLJ1
CARRIER INFO - NONE
SERIAL NUMBER - 1234123414341
SIGNING - production
LOCK STATE - LOCKED
How can i re-install or re-flash "fastboot mode"? I tried flashing OMAP4440 but nothing happened. I've tried to access to fastboot from win7, win8 and ubuntu. In all of them adb works correctly.
It seems that your bootloader is fine. Reinstall driver and fastboot file, and do the right unlock command.
Sent from my Galaxy Nexus using xda premium
samersh72 said:
It seems that your bootloader is fine. Reinstall driver and fastboot file, and do the right unlock command.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Read closer. OP isn't using Windows. lsusb is a Linux command - plus he stated he already tried under Windows and it worked. Under Windows, it seems OP hasn't told device manager what driver the device should use, WHEN connected in fastboot mode.
OP, search ' android udev rules' then follow instructions. And maybe you're not seeing the device under lsusb because you're not allowed to (yet). In the meantime, you can use 'sudo lsusb' to escalate permissions.
Then, install android SDK and/or update your existing versions.
Still, it's not clear, OP, do your hardware keys work? I mean, can you press up or down, and see the other options like Recovery etc?
Sent from my Nexus
bk201doesntexist said:
Read closer. OP isn't using Windows. lsusb is a Linux command - plus he stated he already tried under Windows and it worked. Under Windows, it seems OP hasn't told device manager what driver the device should use, WHEN connected in fastboot mode.
OP, search ' android udev rules' then follow instructions. And maybe you're not seeing the device under lsusb because you're not allowed to (yet). In the meantime, you can use 'sudo lsusb' to escalate permissions.
Then, install android SDK and/or update your existing versions.
Still, it's not clear, OP, do your hardware keys work? I mean, can you press up or down, and see the other options like Recovery etc?
Sent from my Nexus
Click to expand...
Click to collapse
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.
xekin said:
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.
Click to expand...
Click to collapse
anyone has this problem? i mean if there is someone who has a gnex which doesn't response when he pushes up,down buttons?it looks like frozen, and the usb doesn't seem to work
xekin said:
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.
Click to expand...
Click to collapse
Is your user in group "plugdev"? 'gpasswd -a <user> <group>' as root
Run fastboot with root privileges enabled
bk201doesntexist said:
Is your user in group "plugdev"? 'gpasswd -a <user> <group>' as root
Run fastboot with root privileges enabled
Click to expand...
Click to collapse
Thanks
yep, it doesn't work with my user or root. this is what i see with a dmesg when fastboot mode:
hub 2-0:1.0: connect-debounce failed, port 1 disabled
Click to expand...
Click to collapse
Any idea?
xekin said:
Thanks
yep, it doesn't work with my user or root. this is what i see with a dmesg when fastboot mode:
Any idea?
Click to expand...
Click to collapse
seems to be quite an old bug on Ubuntu (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88530)
use another usb port/controller?
are you connecting the device to a USB HUB? More devices connected to the PC?
change usb cables?
try to update your kernel to latest (3.9.x) ?
is this a laptop? try to remove the battery, wait like 10min, turn it on again
same prolem nexus 4
I am having the same problem with my nexus 4 sometimes it connects and then desconnects what can i do ?Please help!! :crying::crying::crying::crying::crying:
xekin said:
More info about:
This is what is shown in fastboot mode:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro
HW VERSION - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLJ1
CARRIER INFO - NONE
SERIAL NUMBER - 1234123414341
SIGNING - production
LOCK STATE - LOCKED
How can i re-install or re-flash "fastboot mode"? I tried flashing OMAP4440 but nothing happened. I've tried to access to fastboot from win7, win8 and ubuntu. In all of them adb works correctly.
Click to expand...
Click to collapse
did u change your bootloader version?
should be PRIMELC03 from stock.. KK15 was the old version. that why u got this issues. just back to stock version (newest).
try boot to odin bootloader (long press volume down + power button). if your phone can boot to odin then install the odin toolkit (pc)