Develop Bugs

Blueangel Don't Register Via Usb

I'm trying to connect to my Blueangel running GPE over the usb-eth bridge.
I'm running gentoo on linux 2.6.12 ( so Its not the known Zaurus register issue ).
Module usbnet is loaded, but no usb0 device.
lsusb shows only my mouse:
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 046d:c012 Logitech, Inc. Optical Mouse
Bus 001 Device 001: ID 0000:0000
Tried this on two different computers, but no luck on any of them :/
Does anyone have any idea what might cause this?
I'm getting the same issue running both Opie ang GPE.

Need help setting up adb & fastboot in Ubuntu

Coonecting my Galaxy Nexus to my laptop and running lsusb shows this
Code:
[email protected]:~/android/android-sdk-linux/tools$ lsusb
Bus 002 Device 003: ID 05c6:9204 Qualcomm, Inc.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 007: ID 04e8:6860 Samsung Electronics Co., Ltd
Bus 001 Device 005: ID 17ef:4816 Lenovo
Bus 001 Device 004: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. Bluetooth Controller
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/android/android-sdk-linux/tools$
So I created /etc/udev/rules.d/51-android.rules to have both samsung and qualcomm VendorID. Now when I run adb devices, it works fine
Code:
[email protected]:~/android/android-sdk-linux/tools$ ./adb devices
List of devices attached
014691490901E018 device
[email protected]:~/android/android-sdk-linux/tools$
but when I go to fastboot mode, nothing shows. for some reason it doesn't work.
Code:
[email protected]:~/android/android-sdk-linux/tools$ ./adb devices
List of devices attached
[email protected]:~/android/android-sdk-linux/tools$
Is there anything I'm missing here?

This is my 51-android.rules file
Code:
[email protected]:~/android/android-sdk-linux/tools$ cat /etc/udev/rules.d/51-android.rules
UBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", OWNER="<yousef>"
UBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", OWNER="<yousef>"
UBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", OWNER="<yousef>"
[email protected]:~/android/android-sdk-linux/tools$

I do not have the < > symbols around my user name in my file. I don't know if that is the problem though.
Sent from my Galaxy Nexus using XDA App

I'll give it a try. Thanks
Sent from my Galaxy Nexus using XDA App

tried on windows too. I can get the phone recognized correctly. But in in the bootlaoder. fastboot revoot-bootloader just shows <waiting for device>. and thats in both ubuntu and windows

I think I'm experiencing the same problem in Ubuntu - the 'waiting for device' problem when trying to fastboot-linux oem unlock. Please post if you make any progress! Thanks!
BTW, I've got a thread on ubuntuforums that's going nowhere at the moment but deals with about the same subject matter. Can't post a link because I'm too new on this forum.

This worked for me: http://forum.xda-developers.com/showthread.php?p=20381664

YDardeer said:
Coonecting my Galaxy Nexus to my laptop and running lsusb shows this
Code:
[email protected]:~/android/android-sdk-linux/tools$ lsusb
Bus 002 Device 003: ID 05c6:9204 Qualcomm, Inc.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 007: ID 04e8:6860 Samsung Electronics Co., Ltd
Bus 001 Device 005: ID 17ef:4816 Lenovo
Bus 001 Device 004: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. Bluetooth Controller
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/android/android-sdk-linux/tools$
So I created /etc/udev/rules.d/51-android.rules to have both samsung and qualcomm VendorID. Now when I run adb devices, it works fine
Code:
[email protected]:~/android/android-sdk-linux/tools$ ./adb devices
List of devices attached
014691490901E018 device
[email protected]:~/android/android-sdk-linux/tools$
but when I go to fastboot mode, nothing shows. for some reason it doesn't work.
Code:
[email protected]:~/android/android-sdk-linux/tools$ ./adb devices
List of devices attached
[email protected]:~/android/android-sdk-linux/tools$
Is there anything I'm missing here?
Click to expand...
Click to collapse
When you are in fast boot you must type fastboot devices and not adb devices

only TWRP on my KF - no software - need help

hi together,
at first, sorry for my bad english, ...i'm from germany.
some time, i was owner of a rooted and flashed KF which worked fine. 6 days before, i installed google play and the keyboard was offline. i went back in twrp 2.2.2.1 and make a wipe and forgot, that i need the software to flash it again. i'm an idiot, i know.
now, i only have twrp in recovery and don't know what to do. i'm not confirm with linux/ubuntu and the handling of soupkit.
facts i have at the moment:
- a KF with twrp 2.2.2.1
- my 2nd pc with a brandnew ubuntu 12.10
- information, that my KF was found on usb in bootloop and twrp, see below:
[email protected]:~$ lsusb
Bus 001 Device 006: ID 18d1:d002 Google Inc.
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
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
Bus 001 Device 009: ID 1949:0006 Lab126
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
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]:~$
"Google Inc" and "Lab126" ist the same. google in bootloop and lab126 in recovery mode.
can anybody help me with ubuntu and soupkit, that i can transfer a flashfile to my KF ?
with best regards, stefan
PROBLEM SOLVED - THX

Does your computer recognize the kf? If it does, then why not transfer a rom to it & flash it in twrp?

BrooklynNY said:
Does your computer recognize the kf? If it does, then why not transfer a rom to it & flash it in twrp?
Click to expand...
Click to collapse
thanks a lot :angel:
five minutes before, i found a threadto do just this :good:
at the moment ii try it and i hop it works with aliendroid v8, ....now i will see if this rom has german language.
and a question: whats in your opinion the best rom for a KF ?

das_es said:
hi together,
at first, sorry for my bad english, ...i'm from germany.
some time, i was owner of a rooted and flashed KF which worked fine. 6 days before, i installed google play and the keyboard was offline. i went back in twrp 2.2.2.1 and make a wipe and forgot, that i need the software to flash it again. i'm an idiot, i know.
now, i only have twrp in recovery and don't know what to do. i'm not confirm with linux/ubuntu and the handling of soupkit.
facts i have at the moment:
- a KF with twrp 2.2.2.1
- my 2nd pc with a brandnew ubuntu 12.10
- information, that my KF was found on usb in bootloop and twrp, see below:
[email protected]:~$ lsusb
Bus 001 Device 006: ID 18d1:d002 Google Inc.
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
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
Bus 001 Device 009: ID 1949:0006 Lab126
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
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]:~$
"Google Inc" and "Lab126" ist the same. google in bootloop and lab126 in recovery mode.
can anybody help me with ubuntu and soupkit, that i can transfer a flashfile to my KF ?
with best regards, stefan
Click to expand...
Click to collapse
Actually, your problem may be easier to fix than you think.
1) Download a ROM of your choosing to your computer (for stock, choose MoDaCo).
2) Boot the device into recovery (use SoupKit if you need to) and select the "Mount" function.
3) Make sure there is an [X] next to Mount SDcard (you should actually see "[X] Unmount SDcard" when it's selected)
4) In Linux, you should get a prompt asking what you want to do with the mounted volume. Select "view folder" or something similar. Or you could open your file manager and look for it under devices.
5) Transfer the ROM to your sdcard.
6) Wipe system, factory reset then install the ROM.

only TWRP on my KF - PROBLEM SOLVED
thx to all, it was easier to solve this problem as i thought.
i'm really happy now
my wife is happy too. now it's her's and i can by an galaxy note 10.1

[Q] Kindle Fire stuck at boot animation after LCD Density change

Hi everyone,this is my first post on the XDA forum.Recently,i had installed the Stock Jelly Bean 4.2.1_r1 for the Kindle Fire made by Hashcode.Things have been working well,untill today.I found an app call LCD density modder(2.4.2) and i installed it.After i apply my density change(160 to 200),the system reboot.However,it only passed the Kindle Fire Red logo and then stuck at the Jelly Bean 4.2.1 animation boot.
I have tried to connect the Kindle Fire to my pc and tried to use the Kindle Fire Utility but my ADB is set at offline.I have tried everything,uninstall driver to normal boot-turn off device trick,but none of them has work.I'm a newbie,so this is really confusing for me right now.If anyone know how to fix this,please help me !!!
P.S:Sorry for my bad English.It isn't my native language !!!
UPDATE:
So I've try using Ubuntu 12.10, install Soupkit, It didn't work: ADB status is Offline.
Switch to Ubuntu 12.04. and tried to test something, and I think maybe there is sth wrong.
First I hit this, with my KF plug in
[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:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8564:1000
Bus 002 Device 007: ID 1949:0005 Lab126
Click to expand...
Click to collapse
Then I remove my KF and did it again, this time it showed this
[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:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8564:1000
Click to expand...
Click to collapse
So my guess it my PC still recognised it as Lab126.
Then I did another test, I type in
sudo gedit /etc/udev/rules.s/51-android.rules
Click to expand...
Click to collapse
And this showed up:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Click to expand...
Click to collapse
So I think that my system need some adjust. Can anyone help me please?
Update: I saw that on when I got lsusb it supposed to say Bus 003 Device 026: ID 1949:0006 Lab126 or something. but I got 0005.
Maybe this is the problem, I don't really know. Can anyone take a look and see what happend to my KF Id.

if you boot to your recovery (twrp) you should have adb available.
then you can set the density back in the build.prop in the system folder.
take care of the permissions !

But i can't boot into TWRP.
My kindle doesn't show up the yellow triangle.It just show up the regular kindle fire logo

gave you a pm ...

I'm trying on Soupkit but it said that "Device Offine", and I really don't know what to do next, first time on Ubuntu and have tried some solutions but they just don't work. Anyone can help?

with ubuntu no drivers are needed - try a other cable first - then maybe contact soupmagnet for further help

Two things...
1) In your PM you said "sudo gedit /etc/udev/rules.d/51-android.rules" opens a blank document, but here you state otherwise. So which is correct?
2) I've seen the PID of 0005 in only one other situation before and it resulted in having to replace the bootloader. But your device has moved past the bootloader and on to the boot animation so your situation may be different...or not. You could try to change your udev rules to match the PID indicated by the device and then reload the udev rules:
Code:
sudo udevadm control --reload-rules
...if that doesn't work, you'll need a factory cable to get the device into fastboot so you can access recovery. Even then, you may be looking at usbboot to fix the bootloader.
"That's a special kind of stupid. The kind that makes me laugh"

1) In your PM you said "sudo gedit /etc/udev/rules.d/51-android.rules" opens a blank document, but here you state otherwise. So which is correct?
Click to expand...
Click to collapse
The PM was wrong, the code when I used was wrong, I type in
Code:
sudo gedit /etc/[B]e[/B]dev/rules.d/51-android.rules
So It was obviously wrong ( but I copy the code from your thread )
Gonna try your suggestion now, Right now I'm in Window so can't try it yet.
Try to get a factory cable in a day or two. May have to build one myself because I live in Vietnam. Or I can try to buy one from China, idk.
Posting the result soon, I hope.

Can one of you guys PM me? I came through a page on the Internet (which XDA won't allow me to post) and I think I found a guy who successfuly solved one similar problem. But I don't understand what he said, so can you help me. The link is on linuxsleuthing blogspot, page :Rubbing Sticks: Lighting The Kindle Fire . Plz have a quick look

raulmadrid1998 said:
Gonna try your suggestion now, Right now I'm in Window so can't try it yet.
Try to get a factory cable in a day or two. May have to build one myself because I live in Vietnam. Or I can try to buy one from China, idk.
Posting the result soon, I hope.
Click to expand...
Click to collapse
What an interesting coincidence...the one other situation where I've seen a PID of 0005 was from a guy in Vietnam. I wonder if there is a connection somehow.
raulmadrid1998 said:
Can one of you guys PM me? I came through a page on the Internet (which XDA won't allow me to post) and I think I found a guy who successfuly solved one similar problem. But I don't understand what he said, so can you help me. The link is on linuxsleuthing blogspot, page :Rubbing Sticks: Lighting The Kindle Fire . Plz have a quick look
Click to expand...
Click to collapse
Everything that guy is talking about, is done automatically in SoupKit when you install it.
Get your factory cable then we can work from there.

Please help
b63 said:
gave you a pm ...
Click to expand...
Click to collapse
My kindles TWRP is gone after i tried installing the kindle os so i can remove jelly bean. Now my kindle wont boot, and wont show up in KFU so i can fix it. When i turn it on it show KINDLE FIRES original logo bright then black outs in like 5 seconds and show it again with a dimmer light. Do you have any idea how i can fix this because ive been searching for 4 weeks now and cant find one thing. thank you.

4 weeks really? Okay well a couple things did you do a full wipe when you flashed stock? My guess is no. What was the charge level of your battery when you flashed update.zip? If you didn't do a full wipe your kindle is stuck trying to handle the data left behind. This requires a factory cable to fix. If your battery was near depleted when you flashed it the problem could be compounded by a 5 second boot loop. My guess is the prior improperly flashing of stock without a full wipe buying a cable and leaving it on charger is your best bet for a fix. Cables can be puchased here http://forum.xda-developers.com/showthread.php?t=1392693 post 9 and worth every penny. Good luck

trouble shooting htc one m8

Hello,
I've been looking into rooting my phone and I have ran into a problem.
I've downloaded everything. adb the files to root my phone etc. But im stuck on trying to find my device
(running kali linux )
i enter the command to locate it in terminal but nothing shows up:
[email protected]:~# adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~# adb devices
List of devices attached
<----- (is just blank)
ive tried running [lsusb] and it doesnt show up either:
[email protected]:~# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 064e:d213 Suyin Corp.
Bus 001 Device 003: ID 04ca:3005 Lite-On Technology Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
it seems like my machine doesnt even say its there. Debugging has been checked off, ive changed the usb input or what ever from charge only to mtp to ptp and none of those work either.
first time posting ever on the form since ive spent three days trying to trouble shoot this but yet to come up with something. please help so i can run my phone as root lol!

nieev said:
Hello,
I've been looking into rooting my phone and I have ran into a problem.
I've downloaded everything. adb the files to root my phone etc. But im stuck on trying to find my device
(running kali linux )
i enter the command to locate it in terminal but nothing shows up:
[email protected]:~# adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~# adb devices
List of devices attached
<----- (is just blank)
ive tried running [lsusb] and it doesnt show up either:
[email protected]:~# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 064e:d213 Suyin Corp.
Bus 001 Device 003: ID 04ca:3005 Lite-On Technology Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
it seems like my machine doesnt even say its there. Debugging has been checked off, ive changed the usb input or what ever from charge only to mtp to ptp and none of those work either.
first time posting ever on the form since ive spent three days trying to trouble shoot this but yet to come up with something. please help so i can run my phone as root lol!
Click to expand...
Click to collapse
EDIT: I hit enter WAY too quick lol
Do you have the proper USB drivers set up?
Check out this link. It probably has the instructions you need, even though it is for Ubuntu.
EDIT#2: I haven't used Linux in forever, but someone I was just talking to said "shouldn't it be sudo adb devices? I think he was right.

Seems like you have a lot of devices, and possibly a USB hub? Make sure you haven't connected through a hub, which can cause issues.
You're booted into OS when trying to issue adb command (which is required) or alternately custom recovery? Some folks mistakenly believe they can connect adb with phone in bootloader (only fastboot works in bootloader - and it has to be in fastboot mode).

woo hoo stupid fix
I figured it out. Anyone who has this same issue as me sometimes switching usb cords works thanks guys