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 all.
I have seen this in another kind of devices but haven't found thread related about Kindle Fire (1st gen).
A little introduction:
- My kindle was in CM10 and I noticed it started to be detected as Unknown Device in Windows, so
- I used TWRP to flash 6.3.1 stock ROM BUT forgot to wipe before flashing and rebooting. In that moment my situation was an endless loop wih the Kindle being rebooted after 15 seconds aproximately.
- I modified a cable to make it "factory cable" but even in fastboot (plain kindle fire logo) the Unknown Device was there.
- After many tries I managed to make a Reset to factory defaults in Android in the 15 seconds
- Currently the kindle is in stock ROM but still is not correctly detected.
Of course, I have re-installed the drivers in my computer and even tried in a fresh windows installation with no previous drivers without luck. Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
So, if some of you have any idea to try, please tell me. I have the factory cable and the back cover of the kindle removed... ready for anything!
Thank you for your time!
soukron said:
Hi all.
Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
Click to expand...
Click to collapse
This is the part I mentioned before about dmesg messages:
Code:
[ 234.956030] usb 2-5: >new full-speed USB device number 4 using ohci_hcd
[ 235.136035] usb 2-5: >device descriptor read/64, error -62
[ 235.420038] usb 2-5: >device descriptor read/64, error -62
[ 235.700026] usb 2-5: >new full-speed USB device number 5 using ohci_hcd
[ 235.880055] usb 2-5: >device descriptor read/64, error -62
[ 236.164040] usb 2-5: >device descriptor read/64, error -62
[ 236.444025] usb 2-5: >new full-speed USB device number 6 using ohci_hcd
[ 236.852030] usb 2-5: >device not accepting address 6, error -62
[ 237.028025] usb 2-5: >new full-speed USB device number 7 using ohci_hcd
[ 237.436025] usb 2-5: >device not accepting address 7, error -62
[ 237.436037] hub 2-0:1.0: >unable to enumerate USB device on port 5
And there's no reference in lsusb:
Code:
[email protected]:~$ lsusb
Bus 001 Device 004: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive
Bus 001 Device 005: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 002: ID 04ca:0022 Lite-On Technology Corp.
Bus 002 Device 003: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/10p, 12M
|__ Port 3: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 4: Dev 3, If 0, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 1, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 2, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 3, Class=HID, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/10p, 480M
|__ Port 9: Dev 5, If 0, Class=>ifc, Driver=rtl8187, 480M
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
soupmagnet said:
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
Click to expand...
Click to collapse
I'm trying to follow this thread http://forum.xda-developers.com/showthread.php?t=1636883 but I don't know how to check if the "short trick" is well performed or not. Is there anything I should notice? At this moment if I make the short trick and plug in the usb connector, nothing seems to be working in the kindle but dmesg is continuously showing errors like previous ones.
Regards,
Are you using Firekit? What command?
"That's a special kind of stupid. The kind that makes me laugh"
I'm still in the step of the process when I make the short trick, plug the usb and the kindle should be detected. Should I try the usbboot commands even when there's no kindle entry in lsusb output?
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
Click to expand...
Click to collapse
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
soukron said:
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
Click to expand...
Click to collapse
Are you using a 32bit or 64bit machine? If you have SoupKit installed, option 2 should have installed 32bit libs, but sometimes it fails...mostly due to Ubuntu servers and them trying to make 32bit libs obsolete. If you're running a 64bit machine, try installing 32bit libs again and see if you get any errors.
Code:
sudo apt-get install ia32-libs
Also since you have SoupKit installed, run it and select option 4 to launch the Firekit. There's really no difference in using Firekit and manually entering the commands for Rekindle but it makes things a little easier. Select "usb_install_fff_twrp". The important thing to know about the "usb_fix_parts..." and "usb_install..." commands in Firekit is that they both use "fastboot boot ..." instead of "fastboot flash ..." to install TWRP and FFF. Meaning, if you reboot or shut the device down before actually installing a bootloader, the device won't turn back on and you'll have to do the shorting trick again.
That being said, from the moment you make the short, you only have about 2 seconds to plug the device in and have Linux detect it before the CPU resets and you have to start all over again.
Hold the power button for 10-15 seconds to make sure the CPU is off before attempting the short.
Launch Firekit and select "usb_install_fff_twrp". When the command is run, you will get the "Waiting for OMAP4 device..." prompt. Let it wait.
To do the shorting trick...
Something I have found to be most useful in this situation is to use a sharp pair of tweezers or safety pin to make the short.
Keep the device flat on a desk or table with the USB connection pointed away from you. Use one hand to hold the short, one hand to plug the device in, and use your body against the other end of the device as leverage as you plug it in.
Using a safety pin, stick the sharp end of the safety pin into the short point and press it in a little to keep it from sliding off when you plug the device in. Squeeze the other end of the safety pin or tweezers to make contact with the metal frame and immediately plug the device in while holding the short.
If the tweezers slip or make contact with the frame before you are ready, hold the power button for 10-15 seconds to make sure the device is completely shut down and try again.
You should see something going on in the terminal to let you know it's working...let it finish.
It might take a few attempts to get the timing right but persistence (and practice) is key...don't give up.
Follow these instructions and I'm positive you'll get it working again. Good luck.
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
soukron said:
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
Click to expand...
Click to collapse
When the OMAP4 device is detected, you will see something similar to this in the terminal:
http://forum.xda-developers.com/attachment.php?attachmentid=1262650&d=1345043823
That will temporarily install the bootloader, which is likely the cause of Linux not being able to detect it in the first place. When you see the yellow triangle on your Kindle, you'll know the Firekit worked. But you still have to permanently install the bootloader via fastboot (or TWRP if accessible) before you reboot the device.
Will it work to get Linux to detect it? Most likely, but there's no way to know for sure until you get a new bootloader installed.
On second thought...
I just realized you may not even have to do that in the first place. Lucky you? If your device is working properly as you said, boot into Android and open up the Terminal Emulator. Make sure the u-boot.bin is on your sdcard and enter the following:
Code:
su
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
reboot
See if that works.
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
soukron said:
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
Click to expand...
Click to collapse
Nope...you need root access to use the 'dd' command.
soupmagnet said:
Nope...you need root access to use the 'dd' command.
Click to expand...
Click to collapse
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
soukron said:
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
Click to expand...
Click to collapse
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds..
Sent from my GT-I8350 using Board Express
prahladvarda said:
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds.
Click to expand...
Click to collapse
Unfortunately, it won't work in this situation.
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...
Alright, this is weird. I hope I don't have a faulty unit.
Basically, fastboot mode is not being detected AT ALL from my computer. Not even sound notification from Windows that something is being connected.
The problem is not the cable or either the drivers, both an Xperia xz1 compact and a Moto x4 are detected normally in fastboot mode (although with Xperia I had to update drivers, since it was just "android device" in device manager...but even the Xperia at least gave me the pop up sound in Windows).
I tried everything in Developer Options (although Moto x4 didn't even need to have debugging on for fastboot mode to work, incredible...).
I don't know what to do, I never seen something like that.
Model is XT1789-04, brand new but apparently already came with unlocked bootloader from eBay (see screenshots)
Beeing able to use fastboot is essential for start modding...
P.S adb in recovery mode works...
Well, I just solved to mistery.
I tried to use a type c - type c cable (never used it before in my life for any Moto or android in general lol) and voila...weird.
But the problem is, no essential fastboot command works. Only the "fastboot devices" works (it shows the Device).
Even something basic as oem device-info gives me error or command error...
Do I have a faulty unit?
Double post, sorry