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.
So I have read the all about KF guide, I read the how to set up adb guide, and I used the KF utility to install my drivers for adb, I checked device manager to make sure I have the correct drivers installed but when I execute "adb devices" there is nothing.. So, I installed ubuntu on a machine, spent hours setting it up for adb, got it all up and running and same thing, adb devices = nothing. So my KF is on 6.3.1 stock software, my goal here is to root, and I'm wondering if it is the new software that is screwing me up?? I already asked if the 6.3 root process will work which someone said it should work just fine.. But I don't know what I'm doing wrong... Any suggestions? I have a friend that is a electrical engineer major who is making me a factory cable... So maybe that is my answer? Thanks
Are you getting an error with adb or are you getting no devices?
I've had usb port problems on my desktop where it wouldn't recognize and ADB device, but switching to a new port worked. Specifically a usb port on a hub, but I imagine this was a very unique case to me, but trying different usb ports is always a good debug step.
Also, usb cables sometimes are bad as well. I have a micro usb cable that only charges, doesn't do any data. I would recommend a new cable as well.
Thirdly, try a different computer if possible. Basically you're trying to isolate the problem is in fact your computer and not your Kindle.
soupmagnet said:
Are you getting an error with adb or are you getting no devices?
Click to expand...
Click to collapse
ADB starts the server, and then says
List of devices attatched
thats it.. So looks like adb is working properly.. Just no devices listed.
superxpro12 said:
I've had usb port problems on my desktop where it wouldn't recognize and ADB device, but switching to a new port worked. Specifically a usb port on a hub, but I imagine this was a very unique case to me, but trying different usb ports is always a good debug step.
Also, usb cables sometimes are bad as well. I have a micro usb cable that only charges, doesn't do any data. I would recommend a new cable as well.
Thirdly, try a different computer if possible. Basically you're trying to isolate the problem is in fact your computer and not your Kindle.
Click to expand...
Click to collapse
I've tried 2 different cables, that will transfer files and charge, and 3 different computers now... My work computer, my home desktop, and my new linux build.. So I don't think its a issue with a cable or a port..
In Windows it's most likely a driver problem. With Linux, you have to make sure you set up your udev rules.
westlandnick said:
So I have read the all about KF guide, I read the how to set up adb guide, and I used the KF utility to install my drivers for adb, I checked device manager to make sure I have the correct drivers installed but when I execute "adb devices" there is nothing.. So, I installed ubuntu on a machine, spent hours setting it up for adb, got it all up and running and same thing, adb devices = nothing. So my KF is on 6.3.1 stock software, my goal here is to root, and I'm wondering if it is the new software that is screwing me up?? I already asked if the 6.3 root process will work which someone said it should work just fine.. But I don't know what I'm doing wrong... Any suggestions? I have a friend that is a electrical engineer major who is making me a factory cable... So maybe that is my answer? Thanks
Click to expand...
Click to collapse
I had the same problem in my Mac environment first time I tried to connect adb. It would not connect until I edited the adb_usb.ini file under my .android directory. If the file doesn't exist, create it and add 0x1949 on a line by itself. If that doesn't work you probably have a driver issue as stated previously.
UK
ukchucktown said:
I had the same problem in my Mac environment first time I tried to connect adb. It would not connect until I edited the adb_usb.ini file under my .android directory. If the file doesn't exist, create it and add 0x1949 on a line by itself. If that doesn't work you probably have a driver issue as stated previously.
UK
Click to expand...
Click to collapse
I think you are right with the driver issue.. Just for fun at home I plugged my HTC Supersonic in and adb didn't see it either, but at work I have set up drivers for my HTC and adb can see it here... And my work computer has that file. I'll try to add that file to my computer at home when I get there and see if it fixes it. Thanks for that, I figured it had to be something simple/stupid.
soupmagnet said:
In Windows it's most likely a driver problem. With Linux, you have to make sure you set up your udev rules.
Click to expand...
Click to collapse
I don't think I set up any udev rules on my linux.. I will check that out as well.
I have a similar problem, and followed probably every adb guide in the forums, along with several other... I bricked my gf's KF accidentally when I was distracted by her son, and missed a step or 2 for the "Kindle Fire Utility", but I THINK the problem started even before that attempting to use the "SuperOneClick" tool to root it... I did everything correctly with the tool BUT from what I've read it is no longer working correctly... The KF is stuck at the boot logo, but I can still turn it on and off... I've added/edited the "adb_usb.ini" file, added myself to the udev group, etc. but the device is still not listed under the "adb devices" command, there is no error, no question marks, no nothing... I've seen it listed as "Google Inc" on some guides under the "lsusb" command, and one with "Lab126" which is what mine is listed as... Also killed/restarted the servers, restarted my computer, shut down my computer, tried different cables (all of which have transfering capabilities), etc. so I am completely lost... Not to mention that the LiveUSB was giving me trouble so instead I erased the Windows 7 partition to fully install Ubuntu 12.04... I've been trying to figure this out for about 3 days to no avail... Any advice???
Thanks in Advance!!!
CJ
(Edit: Just tried the "lsusb" command, and it doesn't even show up like that anymore)
yeah run andadb on your machine do steps 1-4 in terminal http://forum.xda-developers.com/showthread.php?t=1670405 just right click on andadb go to properties permissions allow it to be executed and run it after all 4 steps are done and you have followed the threads instructions use sudo for your fastbboot commands
@Thepooch alright, that took me a BIG step in the right direction, thanks!!! The "lsusb" command now shows that it's connected as "Lab126" again, BUT "adb devices" still comes back with nothing... I'm sooo close, but still so far from getting this thing right...
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse
Bus 002 Device 002: ID 0408:03f5 Quanta Computer, Inc.
Bus 003 Device 002: ID 0bda:0186 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 1949:0006 Lab126
[email protected]:~$ adb kill-server
[email protected]:~$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached
Yeah I'm not seeing the Google driver in the list did you run the sdk and select the top two and Deselect the rest if so that's fine. Power your kindle off type sudo fastboot getvar product plug your kindle in it should power on and terminal output should be product: kindle then type sudo fastboot reboot your kindle will then reboot.
Honestly, I don't know... There was another guide (not sure exactly which one) where I had to install Eclipse and run the sdk and install drivers/platforms from there and I'm not sure exactly which ones it had me install... I tried to do it from the guide that you posted as well but for some reason the part where the sdk was supposed to open etc. didn't work as it was supposed to... The rest worked fine though... I'll have to re-check it, but hopefully that piece of information is what I've been searching for, but at the same time if it is, I'm going to feel even more "special" lol...
Edit: Not sure if the SDK is the same when using Eclipse or not, but the "Android SDK Tools" and "Android SDK Platform Tools" are my first 2 and they were already installed... Did everything you said from there,and I've been "< waiting for device >" for a good 5 minutes now... Is it always this complicated or did I just really screw things up???
Lab126 is your device booted normally or in recovery. As Lab126 you can only issue adb commands. lsusb > Bus 001 Device 005: ID 1949:0100 Lab126
Google inc. is your device in fastboot mode. As Google inc. you can only issue fastboot commands. lsusb > Bus 001 Device 005: ID 18d1:0100 Google Inc.
What seems to be the problem is, what you think to be fastboot is kind of misleading. The stock Kindle ROM has the Kindle Fire logo for its boot animation as well as the bootloader. So, if you're stuck in a boot animation bootloop it could very well seem like you're stuck in fastboot. But that's just a guess.
Enter "adb devices" and see if you're connected.
[Edit:]Also, double check your adb_usb.ini to make sure it's configured properly.
Not sure exactly who you're suggestions are meant to be towards but it fits right along with my problem, and it's put in a much more informative way than I could've put it ... How would I/is it possible for me to get into fastboot while it's still recognized as "Lab126"??? All of my files including "adb_usb.ini" are configured to the best of my knowledge...
When you open adb_usb.ini does it have 0x1949 on its own line and nothing else on that line?
And when you enter "sudo gedit /etc/udev/rules.d/51-android.rules", do you see this...
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTRS{idProduct}=="0006", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTRS{idProduct}=="0100", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Yup, the only difference is on the 51 rules file, I switched "OWNER="root"" to "OWNER="CJ""...
sdfyhpromotions said:
Yup, the only difference is on the 51 rules file, I switched "OWNER="root"" to "OWNER="CJ""...
Click to expand...
Click to collapse
and you can't get adb to connect?
Not in the 9,837 times I've tried it ... Oh, and it was originally "root" until I read somewhere that it's supposed to be you're account username but I'll try to change it back and see if it makes a difference...
Hi to all
I'm trying to flash an aosp self-compiled rom but i've got a problem with fastboot. I'm using an ubuntu machine [12.04] and the fastboot version that came with the ADT IDE.
Even if I'm able to use adb and all of its functions, when i try to use fastboot (e.g. fastboot devices) it do not show me any results.
I've tryed different version of fastboot on different ubuntu machine and different usb port with different cables but nothing changed: no output from fastboot.
If I try to disconnect and then reconnect the device in bootloader mode, i get the infamous message at the bottom of the screen saying "Fastboot Command Read Error -2147483647" and nothing more.
However an old version of fastboot coming from a sdk (maybe an API level 15, i do not remember) on my macbook pro with osx is able to connect and send commands.
While i was searching in this forum for some answer, i've found different threads regarding this error: it maybe be a bug instead of a hw/cable problem?
I'm going to flash an official factory image taken from the google sites and then i'll try again, but what do you suggest?
UPDATE:
Even with the factory image, fastboot came out with the same error...
I'm having the same problem on ubuntu. I don't have a Mac to try. Thanks for the info.
peadarog said:
I'm having the same problem on ubuntu. I don't have a Mac to try. Thanks for the info.
Click to expand...
Click to collapse
Code:
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0666", OWNER="<YOUR_USERNAME>"
This worked for me. For some reason fastboot won't work with mode 0600 as adb
Does this work for you? http://forum.xda-developers.com/showpost.php?p=36772681&postcount=11
from: http://forum.xda-developers.com/showthread.php?t=2099241
He had the same error, and i wasn't able to understand if he got it to work.. I'm also wondering why robetto has a different vendor id..
bodh said:
I'm also wondering why robetto has a different vendor id..
Click to expand...
Click to collapse
that udev rule is an extract from the "Configuring USB Access" section of the Google's Getting Started tutorial. The vendor id (and also the product id) change from samsung to google when you are in fastboot mode.
Good to know. Can i also ask about ATTR{idProduct}=="4e30"- is this only for fastboot as well? I don't have linux, but i've considered setting it up..
bodh said:
Can i also ask about ATTR{idProduct}=="4e30"- is this only for fastboot as well?
Click to expand...
Click to collapse
I don't understand the question.
If you are asking about vendor/attr ids mechanism, I think that this wikipedia page it may help you understand how it's work.
Basically every device connected to your pc is identified by a pair <vendor_id:attr_id>, the first one indicating the company and is assigned per company from PCI-SIG, and the second one is choosen by the manufacturer. In this way your OS can recognise and choose the correct driver/operation to do.
If you are asking why this values change... I can't help you, sorry
What I can tell you is when your phone is normally turned on it's shown with a pair of vend/attr that is different from the one when is in bootloader mode, and the udev entry that I've suggested is useful only in this second scenario for fastboot operation.
Check out the Google's Getting Started tutorial for more infos...
hope this help...
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)
I plugged my phone in ADB debugging but he wasn't recognized by ADB , I typed ADB devices command but not devices attached , so I tried with my Moto E 2015 and I re-typed adb devices and he was recognized by ADB
I'm running Ubuntu 16.04 LTS 32-bits all my softwares are up to date .
If anyone has an idea , please tell it
Thank you
RaiZProduction said:
I plugged my phone in ADB debugging but he wasn't recognized by ADB , I typed ADB devices command but not devices attached , so I tried with my Moto E 2015 and I re-typed adb devices and he was recognized by ADB
I'm running Ubuntu 16.04 LTS 32-bits all my softwares are up to date .
If anyone has an idea , please tell it
Thank you
Click to expand...
Click to collapse
Did you download the platform tools from Android studio?
Have you set up udev rules correctly?
Did you plugged in on an USB 2 Port?
crian said:
Did you download the platform tools from Android studio?
Have you set up udev rules correctly?
Did you plugged in on an USB 2 Port?
Click to expand...
Click to collapse
I plugged into USB 2.0 port ( the same with my moto e )
I don't know how to install the latest platform tool from Android studio web site , here the error when I type Android command on tools :https://hastebin.com/webusumala.md
I don't know what to do at this moment
Please , write some steps on what to do after this
Here my udev rules:https://hastebin.com/ohocobefaq.ini
Tell me if they are correct
crian said:
Did you download the platform tools from Android studio?
Have you set up udev rules correctly?
Did you plugged in on an USB 2 Port?
Click to expand...
Click to collapse
Nevermind I forget to reboot udev server , that's working now thanks for your help