[Q] usb - rs232 converters - Blade General

USB to go works with this device, using kernel from it://github.com/ZTE-BLADE/ZTE-BLADE-2.6.32.git and an special OTG cable.
I tried it with keyboard, mouse and storage, but serial converters do not work.
I compiled the cp210x.ko module and the mos7720.ko, and successfully connected devices.
Code:
<7>[04-09 10:50:12.498753] [12: khubd]hub 1-1:1.0: state 7 ports 4 chg 0000 evt 0010
<7>[04-09 10:50:12.498753] [12: khubd]hub 1-1:1.0: port 4, status 0101, change 0001, 12 Mb/s
<7>[04-09 10:50:12.668756] [12: khubd]hub 1-1:1.0: debounce: port 4: total 100ms stable 100ms status 0x101
<6>[04-09 10:50:12.748751] [12: khubd]usb 1-1.4: new full speed USB device using msm_hsusb_host and address 9
<7>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: default language 0x0409
<7>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: udev 9, busnum 1, minor = 8
<6>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60
<6>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: Product: ELV USB-I2C-Interface
<6>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: Manufacturer: Silicon Labs
<6>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: SerialNumber: VAKVLXWTTHWZAE3L
<7>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: uevent
<7>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: usb_probe_device
<6>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: configuration #1 chosen from 1 choice
<7>[04-09 10:50:12.858751] [12: khubd]usb 1-1.4: adding 1-1.4:1.0 (config #1, interface 0)
<7>[04-09 10:50:12.868760] [12: khubd]usb 1-1.4:1.0: uevent
<7>[04-09 10:50:12.868760] [12: khubd]cp210x 1-1.4:1.0: usb_probe_interface
<7>[04-09 10:50:12.868760] [12: khubd]cp210x 1-1.4:1.0: usb_probe_interface - got id
<6>[04-09 10:50:12.868760] [12: khubd]cp210x 1-1.4:1.0: cp210x converter detected
<6>[04-09 10:50:12.958750] [12: khubd]usb 1-1.4: reset full speed USB device using msm_hsusb_host and address 9
<6>[04-09 10:50:13.068751] [12: khubd]usb 1-1.4: cp210x converter now attached to ttyUSB1
<7>[04-09 10:50:13.068751] [12: khubd]hub 1-1:1.0: state 7 ports 4 chg 0000 evt 0010
Both show similar problems, I got the devices, but when I try to use them I get this line in the log and no real communication.
Code:
<7>[04-09 10:52:26.358770] usb usb1: clear tt buffer port 1, a9 ep1 t00408d80
Did somebody successfully use any serial converter?

Related

[Q] USB Host Mode with ICS 4.0.3 ROM for Kindle Fire

Hi
I recently rooted and installed the CM9 based ICS ROM on Kindle Fire. It works very good. Now I am trying to get it working with the Android Accessory Development Kit (in either of the two modes - accessory or host). Unfortunately I havent been able to get it working. Can somebody confirm if the ROM has USB support enabled or is it still work in progress?
Thanks
Pankaj
The Rom has a bug that disables it...
You will need to mount it in TWRP to transfer files to the Kindle.
Everything else doesn't work, Including the aadk.
That is USB "client." Which as you said is broken in the current ICS ROMS.
USB "Host" is the ability to attach devices like drives and keyboards. This is not functional in Stock, CM7 and ICS.
jfb9301 said:
That is USB "client." Which as you said is broken in the current ICS ROMS.
USB "Host" is the ability to attach devices like drives and keyboards. This is not functional in Stock, CM7 and ICS.
Click to expand...
Click to collapse
USB Host is in ICS.
http://9to5google.com/2011/10/24/an...sb-hosting-brings-gamepadscontrollers-to-all/
engagedtosmile said:
USB Host is in ICS.
Click to expand...
Click to collapse
Yes, it is in ICS. Infact Host Mode support is there from HC 3.1 onwards. What I wanted to know was if its enabled in the CM9 based ICS ROM for Kindle Fire too. I tried but it doesnt seem to.
Kindle Fire OTG Working - First Signs
Hi
I can't post to the Dev threads but using the 17 Jan Kernel build by intersectRaven with the CM9 based ROM, this is what I get in dmesg finally. I have a powered USB hub connected using an OTG cable:
<6>[ 0.020874] usbcore: registered new interface driver usbfs
<6>[ 0.021209] usbcore: registered new interface driver hub
<6>[ 0.021423] usbcore: registered new device driver usb
<6>[ 0.076232] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
<7>[ 0.076538] musb_hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
<7>[ 0.076660] musb_hdrc: MHDRC RTL version 2.0
<7>[ 0.076751] musb_hdrc: setup fifo_mode 4
<7>[ 0.076904] musb_hdrc: 28/31 max ep, 16384/16384 memory
<6>[ 0.077056] musb_hdrc musb_hdrc: USB OTG mode controller at fc0ab000 using DMA, IRQ 124
<6>[ 1.704711] musb_hdrc musb_hdrc: MUSB HDRC host driver
<7>[ 1.710266] drivers/usb/core/inode.c: creating file 'devices'
<7>[ 1.716461] drivers/usb/core/inode.c: creating file '001'
<6>[ 1.722198] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
<7>[ 1.730010] usb usb1: default language 0x0409
<7>[ 1.734680] usb usb1: udev 1, busnum 1, minor = 0
<6>[ 1.739776] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 1.746978] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 1.754730] usb usb1: Product: MUSB HDRC host driver
<6>[ 1.760009] usb usb1: Manufacturer: Linux 2.6.35.7+ musb-hcd
<6>[ 1.766113] usb usb1: SerialNumber: musb_hdrc
<7>[ 1.771240] usb usb1: usb_probe_device
<7>[ 1.775329] usb usb1: configuration #1 chosen from 1 choice
<7>[ 1.781280] usb usb1: adding 1-0:1.0 (config #1, interface 0)
<7>[ 1.787689] hub 1-0:1.0: usb_probe_interface
<7>[ 1.792236] hub 1-0:1.0: usb_probe_interface - got id
<6>[ 1.797637] hub 1-0:1.0: USB hub found
<6>[ 1.801727] hub 1-0:1.0: 1 port detected
<7>[ 1.805938] hub 1-0:1.0: standalone hub
<7>[ 1.810058] hub 1-0:1.0: individual port power switching
<7>[ 1.815795] hub 1-0:1.0: no over-current protection
<7>[ 1.820983] hub 1-0:1.0: power on to power good time: 10ms
<7>[ 1.826904] hub 1-0:1.0: 100mA bus power budget for each child
<7>[ 1.833099] hub 1-0:1.0: local power source is good
<7>[ 1.838378] hub 1-0:1.0: enabling power on all ports
<7>[ 1.843933] drivers/usb/core/inode.c: creating file '001'
<6>[ 2.309783] usbcore: registered new interface driver usbhid
<6>[ 2.315826] usbhid: USB HID core driver
<7>[ 4.811706] hub 1-0:1.0: hub_suspend
<7>[ 4.815551] usb usb1: bus auto-suspend
So these are definite clues that Kindle Fire has OTG working with the the custom kernel build. Unfortunately the last 2 lines above from dmesg are not good as both the hub and usb go to suspend state.
Can somebody help me get these findings over to the intersectRaven's Dev thread on custom kernel.
Can't really help anymore then to offer this note.
In my pursuit of full market access I stumbled upon these features.
<feature name="android.hardware.usb.host" />
<feature name="android.hardware.usb.accessory" />
You may need those in your /system/etc/permissions/tablet_core_hardware.xml at some point.

[Q] how can I debug otg connections

SOLVED: defective otg cable
useful tools:
any android terminal emulator plus root
dmesg
lsusb
2nd otg cable
I cannot seem to get otg working with any of the various USB storage devices I have.
Any ideas on how I can debug this?
If it were normal Linux it would be easy enough, however it's not.
Any suggestions would be appreciated.
Running AOKP buttered right now but sentinel stock and paranoid all do not work either. So it might be a cable or the tablet even.
Hmm not sure but I wonder if the kernel with this rom is missing the fat kernel modules
Thanks
Sent from my Nexus 10 using xda premium
tazmeister said:
I cannot seem to get otg working with any of the various USB storage devices I have.
Click to expand...
Click to collapse
I had the same problems with rooted Stock and various custom ROMs. Try installing "USB OTG Helper [root]" then retest. This app helped get me RW access to OTG storage from SD cards to powered HDD drives in various formats (ext2,3,4 and NTFS).
It worked so well I paid for the donate version just to support the developer. It even has exFAT support although I never tried it. Personally I think it should be part of standard Android.
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
KasF said:
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
Click to expand...
Click to collapse
Thanks more commands to jog my memory and try
I installed a console app and can check dmesg and other stuff.
Lsmod and related seem to be mostly obsolete.
Dmesg shows something is seen but the system keeps failing after this.
I see the same messages regardless of which device I try, powered and unpowered.
<6>[ 6171.135316] s5p-ehci s5p-ehci: S5P EHCI Host Controller
<6>[ 6171.136622] s5p-ehci s5p-ehci: new USB bus registered, assigned bus number 1
<6>[ 6171.137173] s5p-ehci s5p-ehci: irq 103, io mem 0x12110000
<6>[ 6171.145031] s5p-ehci s5p-ehci: USB 0.0 started, EHCI 1.00
<6>[ 6171.145636] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 6171.146150] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 6171.146439] usb usb1: Product: S5P EHCI Host Controller
<6>[ 6171.146925] usb usb1: Manufacturer: Linux 3.4.5-gb44fbc0 ehci_hcd
<6>[ 6171.147202] usb usb1: SerialNumber: s5p-ehci
<6>[ 6171.150947] hub 1-0:1.0: USB hub found
<6>[ 6171.151298] hub 1-0:1.0: 3 ports detected
<6>[ 6171.153725] exynos-ohci exynos-ohci: EXYNOS OHCI Host Controller
<6>[ 6171.156783] exynos-ohci exynos-ohci: new USB bus registered, assigned bus number 2
<6>[ 6171.157031] exynos-ohci exynos-ohci: irq 103, io mem 0x12120000
<6>[ 6171.214330] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
<6>[ 6171.214522] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 6171.214630] usb usb2: Product: EXYNOS OHCI Host Controller
<6>[ 6171.214813] usb usb2: Manufacturer: Linux 3.4.5-gb44fbc0 ohci_hcd
<6>[ 6171.215052] usb usb2: SerialNumber: exynos-ohci
<6>[ 6171.220588] hub 2-0:1.0: USB hub found
<6>[ 6171.220946] hub 2-0:1.0: 3 ports detected
<6>[ 6171.225049] manta_otg manta_otg_work: b_idle -> a_host
<6>[ 6171.705161] usb 2-1: new full-speed USB device number 2 using exynos-ohci
<3>[ 6171.835100] usb 2-1: device descriptor read/64, error -62
<3>[ 6172.070121] usb 2-1: device descriptor read/64, error -62
<6>[ 6172.300093] usb 2-1: new full-speed USB device number 3 using exynos-ohci
<3>[ 6172.430142] usb 2-1: device descriptor read/64, error -62
<3>[ 6172.665754] usb 2-1: device descriptor read/64, error -62
<6>[ 6172.895140] usb 2-1: new full-speed USB device number 4 using exynos-ohci
<3>[ 6173.305043] usb 2-1: device not accepting address 4, error -62
<6>[ 6173.430032] usb 2-1: new full-speed USB device number 5 using exynos-ohci
<3>[ 6173.840038] usb 2-1: device not accepting address 5, error -62
<3>[ 6173.840490] hub 2-0:1.0: unable to enumerate USB device on port 1
Sent from my Nexus 10 using xda premium
None of the org helper apps have helped.
I don't think the org cable is bad though maybe this detail means otherwise
one device starts charging itself of the musb port when i plug it in.
Sent from my Nexus 10 using xda premium
KasF said:
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
Click to expand...
Click to collapse
udevadm doesn't seem to be present but lsusb lists 2 devices when I have something plugged in.
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Sent from my Nexus 10 using xda premium
ok problem solved.
The final debugging step was to "get another otg cable and test to make sure the first otg cable isn't defective"
Since I only owned a single OTG cable at the start, it was sort of difficult to perform this ultimate debug step.
But once I tried a different cable, almost everything worked just fine.
Only my 64gb micro-sd cards gave me a little trouble, but they all work now.

[Q] Usbnet not working: tablet or adapter fault?

Some times ago I bought a made-in-china usb to ethernet adapter for my Nexus 7 tilapia with CM 10, and it worked well.
Now it doesn't work anymore, and I supposed it's adapter fault. So I bought a usb-to-lan adapter by Lindy. It does not work as well.
How can I say for sure it's tablet or adapter fault?
up.
You'd probably get answers if you posted to your devices forums, this is for the N7 2013 (flo and deb).
As for how, I'd imagine you can see in the logs.
EDIT: It appears a helpful mod has moved it to the right section.
I can't find the tilapia section. Is there not one section for older models?
I get this log from dmesg. It seems that device is recognized. It doesn't report any error, but it don't work. Even the adapter leds doesn't light up.
Code:
tegra-otg tegra-otg: SUSPEND --> HOST
phy->instance = 0, phy->xcvr_setup_value = 58
create_regulator: fixed_reg_en_avdd_hdmi_usb_a01: Failed to create debugfs directory
tegra_usb_phy_open instance 0 MAX77663_IRQ_ACOK_RISING
tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
tegra-ehci tegra-ehci.0: irq 52, io mem 0x7d000000
tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: Tegra EHCI Host Controller
usb usb2: Manufacturer: Linux 3.1.10-g30c5396 ehci_hcd
usb usb2: SerialNumber: tegra-ehci.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Wake39 for irq=52
Enabling wake39
INOK=L
smb347_charger: [cable_type_detect] Reg39 : 0x11
smb347_charger: [cable_type_detect] Reg3F : 0x00
USBIN=0
tegra_ehci_irq: no device connected before suspend
tegra-otg tegra-otg: HOST --> SUSPEND
Wake39 for irq=52
Disabling wake39
tegra-ehci tegra-ehci.0: remove, state 4
usb usb2: USB disconnect, device number 1
tegra-ehci tegra-ehci.0: USB bus 2 deregistered
tegra-otg tegra-otg: SUSPEND --> SUSPEND
INOK=H
========================================================
battery_callback usb_cable_state = 0
========================================================
Lucas Malor said:
I can't find the tilapia section. Is there not one section for older models?
I get this log from dmesg:
PHP:
tegra-otg tegra-otg: SUSPEND --> HOST
phy->instance = 0, phy->xcvr_setup_value = 58
create_regulator: fixed_reg_en_avdd_hdmi_usb_a01: Failed to create debugfs directory
tegra_usb_phy_open instance 0 MAX77663_IRQ_ACOK_RISING
tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
tegra-ehci tegra-ehci.0: irq 52, io mem 0x7d000000
tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: Tegra EHCI Host Controller
usb usb2: Manufacturer: Linux 3.1.10-g30c5396 ehci_hcd
usb usb2: SerialNumber: tegra-ehci.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Wake39 for irq=52
Enabling wake39
INOK=L
smb347_charger: [cable_type_detect] Reg39 : 0x11
smb347_charger: [cable_type_detect] Reg3F : 0x00
USBIN=0
tegra_ehci_irq: no device connected before suspend
tegra-otg tegra-otg: HOST --> SUSPEND
Wake39 for irq=52
Disabling wake39
tegra-ehci tegra-ehci.0: remove, state 4
usb usb2: USB disconnect, device number 1
tegra-ehci tegra-ehci.0: USB bus 2 deregistered
tegra-otg tegra-otg: SUSPEND --> SUSPEND
INOK=H
========================================================
battery_callback usb_cable_state = 0
========================================================
It seems that device is recognized. It doesn't report any error, but it don't work. Even the adapter leds doesn't light up.
Click to expand...
Click to collapse
Looks like a mod moved it into the right section, your post is now in the correct area, for future reference this is the link to the N7 2012 section.
As for the issue at hand, it's possible the USB port is dirty or the cable is dirty or damaged.
mdamaged said:
for future reference this is the link to the N7 2012 section.
Click to expand...
Click to collapse
Good, thank you.
mdamaged said:
it's possible the USB port is dirty or the cable is dirty or damaged.
Click to expand...
Click to collapse
Well, it could be the cable, but it's a brand new item and the adapter is recognized. I think the port is ok, I can connect the device to my PC.
Lucas Malor said:
Good, thank you.
Well, it could be the cable, but it's a brand new item and the adapter is recognized. I think the port is ok, I can connect the device to my PC.
Click to expand...
Click to collapse
Assuming you know for sure your device has a driver for that adapter, maybe the adapter is just poorly made, or you may have to do some additional setup steps in a shell to get it to come up.
I don't know if there are no compatible drivers. The official site says the adapter is compatible with Linux, and it does not provide any drivers. And it says it can be used with tablets. But I just noticed it doesn't say it's compatible with Android. Yes, it's Linux, but it's a completely different implementation... and furthermore it doesn't say it can be used with smartphones. So I start to think this damned adapter is not compatible with ARM architectures...

Stuck with no rom and no drivers, what can i do?

Hello everybody,
I just did a great mistakes, i tried to copy the secondary rom to primary slot with multirom TWRP V 3.0.0.0 , so it started to format the primary slot and it failed... and now i can't even boot my secondary rom because i don't have slot partition with kexec-hardboot patch anymore...
Also i can't install the drivers for windows 10 x64 to use the fastboot mode because i need to "Enable usb debugging on the device" to do it...
What's the best option to retrieve my secondary rom? Please help me :crying:
Thank you.
edit: should i do a hard reset?
For fastboot you do not need to enable usb debugging, only for connecting by adb.
Nevertheless to use fastboot, you need to have your device unlocked and to put it into fastboot mode. From there you can start / flash the OP you would like to.
If your device is not unlocked, you will be asked for a device reset which wll erase all the data on your device.
Btw.: using OSx / Linux is much more easy when it comes to flashing / debugging Android.
AndDiSa said:
For fastboot you do not need to enable usb debugging, only for connecting by adb.
Nevertheless to use fastboot, you need to have your device unlocked and to put it into fastboot mode. From there you can start / flash the OP you would like to.
If your device is not unlocked, you will be asked for a device reset which wll erase all the data on your device.
Btw.: using OSx / Linux is much more easy when it comes to flashing / debugging Android.
Click to expand...
Click to collapse
Thanks a million for your reply AndDiSa ! To be honest i was completely desperate...
The bootloader is unlocked, here is a photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried these commands in the terminal on my ubuntu laptop:
Code:
sudo add-apt-repository ppa:phablet-team/tools
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
I connected my nexus in fastboot mode via USB port and i did :
Code:
sudo fastboot devices
But no devices appears. i did something wrong?
Thank you.
You need to adapt your udev-rules, i.e create a file named "51-android.rules" in /etc/udev/rules.d and put the following content into it, but replace the owner name by your login name:
Code:
# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="ds"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="ds"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="ds"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="ds"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="ds"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="ds"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="ds"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="ds"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="ds"
# adb protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d002", MODE="0600", OWNER="ds"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="ds"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="ds"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="ds"
# adb protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="ds"
# fastboot protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="ds"
# adb protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="ds"
# fastboot protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="ds"
##########################################################################################
# my own devices
##########################################################################################
# Google Nexus 7 16 Gb Bootloader & recovery mode
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="ds" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="ds" # Recovery
# Google Nexus 7 16 Gb PTP mode (camera)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e43", MODE="0666", OWNER="ds" # PTP media
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="ds" # PTP media with USB debug on
# Google Nexus 7 16 Gb MTP mode (multimedia device)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0666", OWNER="ds" # MTP media
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="ds" # MTP media with USB debug on
# Google Nexus 7 MTP mode : automatic unmount when unplugged
ENV{ID_MODEL}=="Nexus", ENV{ID_MODEL_ID}=="4e41", ACTION=="remove", RUN+="/usr/bin/fusermount -u /media/nexus7"
ENV{ID_MODEL}=="Nexus", ENV{ID_MODEL_ID}=="4e42", ACTION=="remove", RUN+="/usr/bin/fusermount -u /media/nexus7"
AndDiSa said:
You need to adapt your udev-rules, i.e create a file named "51-android.rules" in /etc/udev/rules.d and put the following content into it, but replace the owner name by your login name:
Click to expand...
Click to collapse
Thanks again for your help.
So i typed this in the terminal:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
then i copied/pasted this:
Code:
# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="mikael"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="mikael"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="mikael"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="mikael"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="mikael"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="mikael"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="mikael"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="mikael"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="mikael"
# adb protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d002", MODE="0600", OWNER="mikael"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="mikael"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="mikael"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="mikael"
# adb protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="mikael"
# fastboot protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="mikael"
# adb protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="mikael"
# fastboot protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="mikael"
##########################################################################################
# my own devices
##########################################################################################
# Google Nexus 7 16 Gb Bootloader & recovery mode
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="mikael" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="mikael" # Recovery
# Google Nexus 7 16 Gb PTP mode (camera)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e43", MODE="0666", OWNER="mikael" # PTP media
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="mikael" # PTP media with USB debug on
# Google Nexus 7 16 Gb MTP mode (multimedia device)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0666", OWNER="mikael" # MTP media
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="mikael" # MTP media with USB debug on
# Google Nexus 7 MTP mode : automatic unmount when unplugged
ENV{ID_MODEL}=="Nexus", ENV{ID_MODEL_ID}=="4e41", ACTION=="remove", RUN+="/usr/bin/fusermount -u /media/nexus7"
ENV{ID_MODEL}=="Nexus", ENV{ID_MODEL_ID}=="4e42", ACTION=="remove", RUN+="/usr/bin/fusermount -u /media/nexus7"
Is it ok?
I saved in gedit and quit, then i connected the Nexus 7 via USB and i tried this :
Code:
lsusb
Sadly the nexus 7 doesn't appear. :/
I'm on ubuntu 14.04 LTS.
First you have to restart the udev subsystem.
# sudo udevadm control --reload-rules
should do the trick
Sent from my Nexus 7 using XDA-Developers mobile app
AndDiSa said:
First you have to restart the udev subsystem.
# sudo udevadm control --reload-rules
should do the trick
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you but
Code:
sudo udevadm control --reload-rules
and still doesn't work , i also reboot the laptop but the Nexus still not appears with
Code:
lsusb
Do you see that a device is connected?
You can have a look with dmesg, probably this will give you a hint what might be wrong ...
Sent from my Nexus 7 using XDA-Developers mobile app
AndDiSa said:
Do you see that a device is connected?
You can have a look with dmesg, probably this will give you a hint what might be wrong ...
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
I see no device connected at the right (launch bar). The Nexus 7 must be on the bootloader, right?
I did a:
Code:
dmesg
but the list is too long so i did this:
Code:
dmesg | grep -i usb
and here is the result:
Code:
[ 0.216934] ACPI: bus type USB registered
[ 0.216966] usbcore: registered new interface driver usbfs
[ 0.216981] usbcore: registered new interface driver hub
[ 0.217015] usbcore: registered new device driver usb
[ 1.055826] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.056014] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 1.071266] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 1.071331] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.071334] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.071336] usb usb1: Product: EHCI Host Controller
[ 1.071339] usb usb1: Manufacturer: Linux 3.16.0-77-generic ehci_hcd
[ 1.071341] usb usb1: SerialNumber: 0000:00:1a.0
[ 1.071509] hub 1-0:1.0: USB hub found
[ 1.071835] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 1.087258] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 1.087314] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.087316] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.087319] usb usb2: Product: EHCI Host Controller
[ 1.087321] usb usb2: Manufacturer: Linux 3.16.0-77-generic ehci_hcd
[ 1.087324] usb usb2: SerialNumber: 0000:00:1d.0
[ 1.087498] hub 2-0:1.0: USB hub found
[ 1.087705] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.087741] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.383076] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 1.516033] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[ 1.516036] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.516334] hub 1-1:1.0: USB hub found
[ 1.626892] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 1.759266] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[ 1.759277] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.759696] hub 2-1:1.0: USB hub found
[ 127.148971] usb 2-1.2: new full-speed USB device number 3 using ehci-pci
[ 127.220913] usb 2-1.2: device descriptor read/64, error -32
[ 127.396785] usb 2-1.2: device descriptor read/64, error -32
[ 127.572661] usb 2-1.2: new full-speed USB device number 4 using ehci-pci
[ 127.644611] usb 2-1.2: device descriptor read/64, error -32
[ 127.820489] usb 2-1.2: device descriptor read/64, error -32
[ 127.996359] usb 2-1.2: new full-speed USB device number 5 using ehci-pci
[ 128.404080] usb 2-1.2: device not accepting address 5, error -32
[ 128.476022] usb 2-1.2: new full-speed USB device number 6 using ehci-pci
[ 128.883740] usb 2-1.2: device not accepting address 6, error -32
[ 128.883854] usb 2-1-port2: unable to enumerate USB device
[ 1164.689944] usb 2-1.2: new full-speed USB device number 7 using ehci-pci
[ 1164.761892] usb 2-1.2: device descriptor read/64, error -32
[ 1164.937766] usb 2-1.2: device descriptor read/64, error -32
[ 1165.113648] usb 2-1.2: new full-speed USB device number 8 using ehci-pci
[ 1165.185595] usb 2-1.2: device descriptor read/64, error -32
[ 1165.361463] usb 2-1.2: device descriptor read/64, error -32
[ 1165.537339] usb 2-1.2: new full-speed USB device number 9 using ehci-pci
[ 1165.945049] usb 2-1.2: device not accepting address 9, error -32
[ 1166.017002] usb 2-1.2: new full-speed USB device number 10 using ehci-pci
[ 1166.424715] usb 2-1.2: device not accepting address 10, error -32
[ 1166.424838] usb 2-1-port2: unable to enumerate USB device
[ 1167.671834] usb 2-1.2: new full-speed USB device number 11 using ehci-pci
[ 1167.743778] usb 2-1.2: device descriptor read/64, error -32
[ 1167.919650] usb 2-1.2: device descriptor read/64, error -32
[ 1168.095525] usb 2-1.2: new full-speed USB device number 12 using ehci-pci
[ 1168.167482] usb 2-1.2: device descriptor read/64, error -32
[ 1168.343367] usb 2-1.2: device descriptor read/64, error -32
[ 1168.519237] usb 2-1.2: new full-speed USB device number 13 using ehci-pci
[ 1168.926938] usb 2-1.2: device not accepting address 13, error -32
[ 1168.998888] usb 2-1.2: new full-speed USB device number 14 using ehci-pci
[ 1169.406607] usb 2-1.2: device not accepting address 14, error -32
[ 1169.406837] usb 2-1-port2: unable to enumerate USB device
[ 1170.653717] usb 2-1.2: new full-speed USB device number 15 using ehci-pci
[ 1170.725665] usb 2-1.2: device descriptor read/64, error -32
[ 1170.901540] usb 2-1.2: device descriptor read/64, error -32
[ 1171.077414] usb 2-1.2: new full-speed USB device number 16 using ehci-pci
[ 1171.149379] usb 2-1.2: device descriptor read/64, error -32
[ 1171.325251] usb 2-1.2: device descriptor read/64, error -32
[ 1171.501120] usb 2-1.2: new full-speed USB device number 17 using ehci-pci
[ 1171.908831] usb 2-1.2: device not accepting address 17, error -32
[ 1171.980775] usb 2-1.2: new full-speed USB device number 18 using ehci-pci
[ 1172.388492] usb 2-1.2: device not accepting address 18, error -32
[ 1172.388674] usb 2-1-port2: unable to enumerate USB device
[ 1173.611623] usb 2-1.2: new full-speed USB device number 19 using ehci-pci
[ 1173.683570] usb 2-1.2: device descriptor read/64, error -32
[ 1173.859443] usb 2-1.2: device descriptor read/64, error -32
[ 1174.035317] usb 2-1.2: new full-speed USB device number 20 using ehci-pci
[ 1174.107268] usb 2-1.2: device descriptor read/64, error -32
[ 1174.283147] usb 2-1.2: device descriptor read/64, error -32
[ 1174.459019] usb 2-1.2: new full-speed USB device number 21 using ehci-pci
[ 1174.866726] usb 2-1.2: device not accepting address 21, error -32
[ 1174.938670] usb 2-1.2: new full-speed USB device number 22 using ehci-pci
[ 1175.346402] usb 2-1.2: device not accepting address 22, error -32
[ 1175.346491] usb 2-1-port2: unable to enumerate USB device
[ 1176.553538] usb 2-1.2: new full-speed USB device number 23 using ehci-pci
[ 1176.625484] usb 2-1.2: device descriptor read/64, error -32
[ 1176.801357] usb 2-1.2: device descriptor read/64, error -32
[ 1176.977233] usb 2-1.2: new full-speed USB device number 24 using ehci-pci
[ 1177.049183] usb 2-1.2: device descriptor read/64, error -32
[ 1177.225067] usb 2-1.2: device descriptor read/64, error -32
[ 1177.400937] usb 2-1.2: new full-speed USB device number 25 using ehci-pci
[ 1177.808651] usb 2-1.2: device not accepting address 25, error -32
[ 1177.880600] usb 2-1.2: new full-speed USB device number 26 using ehci-pci
[ 1178.288288] usb 2-1.2: device not accepting address 26, error -32
[ 1178.288430] usb 2-1-port2: unable to enumerate USB device
[ 1179.495452] usb 2-1.2: new full-speed USB device number 27 using ehci-pci
[ 1179.567400] usb 2-1.2: device descriptor read/64, error -32
[ 1179.743262] usb 2-1.2: device descriptor read/64, error -32
[ 1179.919156] usb 2-1.2: new full-speed USB device number 28 using ehci-pci
[ 1179.991091] usb 2-1.2: device descriptor read/64, error -32
[ 1180.166974] usb 2-1.2: device descriptor read/64, error -32
[ 1180.342855] usb 2-1.2: new full-speed USB device number 29 using ehci-pci
[ 1180.750564] usb 2-1.2: device not accepting address 29, error -32
[ 1180.822521] usb 2-1.2: new full-speed USB device number 30 using ehci-pci
[ 1181.230232] usb 2-1.2: device not accepting address 30, error -32
[ 1181.230430] usb 2-1-port2: unable to enumerate USB device
[ 1181.378102] usb 2-1.2: new full-speed USB device number 31 using ehci-pci
[ 1181.450066] usb 2-1.2: device descriptor read/64, error -32
[ 1181.625947] usb 2-1.2: device descriptor read/64, error -32
[ 1181.801819] usb 2-1.2: new full-speed USB device number 32 using ehci-pci
[ 1181.873778] usb 2-1.2: device descriptor read/64, error -32
[ 1182.049641] usb 2-1.2: device descriptor read/64, error -32
[ 1182.225542] usb 2-1.2: new full-speed USB device number 33 using ehci-pci
[ 1182.633227] usb 2-1.2: device not accepting address 33, error -32
[ 1182.705178] usb 2-1.2: new full-speed USB device number 34 using ehci-pci
[ 1183.112887] usb 2-1.2: device not accepting address 34, error -32
[ 1183.113077] usb 2-1-port2: unable to enumerate USB device
[ 1184.320033] usb 2-1.2: new full-speed USB device number 35 using ehci-pci
[ 1184.391982] usb 2-1.2: device descriptor read/64, error -32
[ 1184.567861] usb 2-1.2: device descriptor read/64, error -32
[ 1184.743733] usb 2-1.2: new full-speed USB device number 36 using ehci-pci
[ 1184.815694] usb 2-1.2: device descriptor read/64, error -32
[ 1184.991554] usb 2-1.2: device descriptor read/64, error -32
[ 1185.167431] usb 2-1.2: new full-speed USB device number 37 using ehci-pci
[ 1185.575142] usb 2-1.2: device not accepting address 37, error -32
[ 1185.647093] usb 2-1.2: new full-speed USB device number 38 using ehci-pci
[ 1186.054800] usb 2-1.2: device not accepting address 38, error -32
[ 1186.054906] usb 2-1-port2: unable to enumerate USB device
[ 1186.202710] usb 2-1.2: new full-speed USB device number 39 using ehci-pci
[ 1186.274647] usb 2-1.2: device descriptor read/64, error -32
[ 1186.450521] usb 2-1.2: device descriptor read/64, error -32
[ 1186.626399] usb 2-1.2: new full-speed USB device number 40 using ehci-pci
[ 1186.698347] usb 2-1.2: device descriptor read/64, error -32
[ 1186.874218] usb 2-1.2: device descriptor read/64, error -32
[ 1187.050099] usb 2-1.2: new full-speed USB device number 41 using ehci-pci
[ 1187.457807] usb 2-1.2: device not accepting address 41, error -32
[ 1187.529760] usb 2-1.2: new full-speed USB device number 42 using ehci-pci
[ 1187.937468] usb 2-1.2: device not accepting address 42, error -32
[ 1187.937568] usb 2-1-port2: unable to enumerate USB device
[ 1188.097370] usb 2-1.2: new full-speed USB device number 43 using ehci-pci
[ 1188.169306] usb 2-1.2: device descriptor read/64, error -32
[ 1188.345215] usb 2-1.2: device descriptor read/64, error -32
[ 1188.521064] usb 2-1.2: new full-speed USB device number 44 using ehci-pci
[ 1188.593010] usb 2-1.2: device descriptor read/64, error -32
[ 1188.768882] usb 2-1.2: device descriptor read/64, error -32
[ 1188.944755] usb 2-1.2: new full-speed USB device number 45 using ehci-pci
[ 1189.352467] usb 2-1.2: device not accepting address 45, error -32
[ 1189.424431] usb 2-1.2: new full-speed USB device number 46 using ehci-pci
[ 1189.832127] usb 2-1.2: device not accepting address 46, error -32
[ 1189.832329] usb 2-1-port2: unable to enumerate USB device
[ 1191.039274] usb 2-1.2: new full-speed USB device number 47 using ehci-pci
[ 1191.111227] usb 2-1.2: device descriptor read/64, error -32
[ 1191.287097] usb 2-1.2: device descriptor read/64, error -32
[ 1191.462969] usb 2-1.2: new full-speed USB device number 48 using ehci-pci
[ 1191.534920] usb 2-1.2: device descriptor read/64, error -32
[ 1191.710795] usb 2-1.2: device descriptor read/64, error -32
[ 1191.886671] usb 2-1.2: new full-speed USB device number 49 using ehci-pci
[ 1192.294399] usb 2-1.2: device not accepting address 49, error -32
[ 1192.366333] usb 2-1.2: new full-speed USB device number 50 using ehci-pci
[ 1192.774038] usb 2-1.2: device not accepting address 50, error -32
[ 1192.774174] usb 2-1-port2: unable to enumerate USB device
[ 1192.921943] usb 2-1.2: new full-speed USB device number 51 using ehci-pci
[ 1192.993888] usb 2-1.2: device descriptor read/64, error -32
[ 1193.169758] usb 2-1.2: device descriptor read/64, error -32
[ 1193.345637] usb 2-1.2: new full-speed USB device number 52 using ehci-pci
[ 1193.417586] usb 2-1.2: device descriptor read/64, error -32
[ 1193.593462] usb 2-1.2: device descriptor read/64, error -32
[ 1193.769337] usb 2-1.2: new full-speed USB device number 53 using ehci-pci
[ 1194.177063] usb 2-1.2: device not accepting address 53, error -32
[ 1194.248996] usb 2-1.2: new full-speed USB device number 54 using ehci-pci
[ 1194.656706] usb 2-1.2: device not accepting address 54, error -32
[ 1194.656827] usb 2-1-port2: unable to enumerate USB device
[ 1195.863855] usb 2-1.2: new full-speed USB device number 55 using ehci-pci
[ 1195.935803] usb 2-1.2: device descriptor read/64, error -32
[ 1196.111679] usb 2-1.2: device descriptor read/64, error -32
[ 1196.287555] usb 2-1.2: new full-speed USB device number 56 using ehci-pci
[ 1196.359502] usb 2-1.2: device descriptor read/64, error -32
[ 1196.535377] usb 2-1.2: device descriptor read/64, error -32
[ 1196.711261] usb 2-1.2: new full-speed USB device number 57 using ehci-pci
[ 1197.118963] usb 2-1.2: device not accepting address 57, error -32
[ 1197.190950] usb 2-1.2: new full-speed USB device number 58 using ehci-pci
[ 1197.598624] usb 2-1.2: device not accepting address 58, error -32
[ 1197.598743] usb 2-1-port2: unable to enumerate USB device
[ 1198.817761] usb 2-1.2: new full-speed USB device number 59 using ehci-pci
[ 1198.889710] usb 2-1.2: device descriptor read/64, error -32
[ 1199.065585] usb 2-1.2: device descriptor read/64, error -32
[ 1199.241460] usb 2-1.2: new full-speed USB device number 60 using ehci-pci
[ 1199.313407] usb 2-1.2: device descriptor read/64, error -32
[ 1199.489284] usb 2-1.2: device descriptor read/64, error -32
[ 1199.665161] usb 2-1.2: new full-speed USB device number 61 using ehci-pci
[ 1200.072869] usb 2-1.2: device not accepting address 61, error -32
[ 1200.144822] usb 2-1.2: new full-speed USB device number 62 using ehci-pci
[ 1200.552532] usb 2-1.2: device not accepting address 62, error -32
[ 1200.552618] usb 2-1-port2: unable to enumerate USB device
[ 1201.771665] usb 2-1.2: new full-speed USB device number 63 using ehci-pci
[ 1201.843617] usb 2-1.2: device descriptor read/64, error -32
[ 1202.019493] usb 2-1.2: device descriptor read/64, error -32
[ 1202.195369] usb 2-1.2: new full-speed USB device number 64 using ehci-pci
[ 1202.267315] usb 2-1.2: device descriptor read/64, error -32
[ 1202.443200] usb 2-1.2: device descriptor read/64, error -32
[ 1202.619070] usb 2-1.2: new full-speed USB device number 65 using ehci-pci
[ 1203.026778] usb 2-1.2: device not accepting address 65, error -32
[ 1203.098728] usb 2-1.2: new full-speed USB device number 66 using ehci-pci
[ 1203.506438] usb 2-1.2: device not accepting address 66, error -32
[ 1203.506623] usb 2-1-port2: unable to enumerate USB device
[ 1204.725574] usb 2-1.2: new full-speed USB device number 67 using ehci-pci
[ 1204.797527] usb 2-1.2: device descriptor read/64, error -32
[ 1204.973400] usb 2-1.2: device descriptor read/64, error -32
[ 1205.149271] usb 2-1.2: new full-speed USB device number 68 using ehci-pci
[ 1205.221259] usb 2-1.2: device descriptor read/64, error -32
[ 1205.397108] usb 2-1.2: device descriptor read/64, error -32
[ 1205.572977] usb 2-1.2: new full-speed USB device number 69 using ehci-pci
[ 1205.980685] usb 2-1.2: device not accepting address 69, error -32
[ 1206.052638] usb 2-1.2: new full-speed USB device number 70 using ehci-pci
[ 1206.460358] usb 2-1.2: device not accepting address 70, error -32
[ 1206.460571] usb 2-1-port2: unable to enumerate USB device
[ 1207.667494] usb 2-1.2: new full-speed USB device number 71 using ehci-pci
[ 1207.739443] usb 2-1.2: device descriptor read/64, error -32
[ 1207.915313] usb 2-1.2: device descriptor read/64, error -32
[ 1208.091193] usb 2-1.2: new full-speed USB device number 72 using ehci-pci
[ 1208.163142] usb 2-1.2: device descriptor read/64, error -32
[ 1208.339015] usb 2-1.2: device descriptor read/64, error -32
[ 1208.514893] usb 2-1.2: new full-speed USB device number 73 using ehci-pci
[ 1208.922604] usb 2-1.2: device not accepting address 73, error -32
[ 1208.994556] usb 2-1.2: new full-speed USB device number 74 using ehci-pci
[ 1209.402261] usb 2-1.2: device not accepting address 74, error -32
[ 1209.402380] usb 2-1-port2: unable to enumerate USB device
[ 1209.550156] usb 2-1.2: new full-speed USB device number 75 using ehci-pci
[ 1209.622107] usb 2-1.2: device descriptor read/64, error -32
[ 1209.797982] usb 2-1.2: device descriptor read/64, error -32
[ 1209.973858] usb 2-1.2: new full-speed USB device number 76 using ehci-pci
[ 1210.045806] usb 2-1.2: device descriptor read/64, error -32
[ 1210.221692] usb 2-1.2: device descriptor read/64, error -32
[ 1210.397563] usb 2-1.2: new full-speed USB device number 77 using ehci-pci
[ 1210.805301] usb 2-1.2: device not accepting address 77, error -32
[ 1210.877229] usb 2-1.2: new full-speed USB device number 78 using ehci-pci
[ 1211.284944] usb 2-1.2: device not accepting address 78, error -32
[ 1211.285030] usb 2-1-port2: unable to enumerate USB device
[ 1212.492078] usb 2-1.2: new full-speed USB device number 79 using ehci-pci
[ 1212.564026] usb 2-1.2: device descriptor read/64, error -32
[ 1212.739898] usb 2-1.2: device descriptor read/64, error -32
[ 1212.915782] usb 2-1.2: new full-speed USB device number 80 using ehci-pci
[ 1212.987734] usb 2-1.2: device descriptor read/64, error -32
[ 1213.163626] usb 2-1.2: device descriptor read/64, error -32
[ 1213.339475] usb 2-1.2: new full-speed USB device number 81 using ehci-pci
[ 1213.747185] usb 2-1.2: device not accepting address 81, error -32
[ 1213.819135] usb 2-1.2: new full-speed USB device number 82 using ehci-pci
[ 1214.226858] usb 2-1.2: device not accepting address 82, error -32
[ 1214.226995] usb 2-1-port2: unable to enumerate USB device
[ 1214.374738] usb 2-1.2: new full-speed USB device number 83 using ehci-pci
[ 1214.446687] usb 2-1.2: device descriptor read/64, error -32
[ 1214.622559] usb 2-1.2: device descriptor read/64, error -32
[ 1214.798461] usb 2-1.2: new full-speed USB device number 84 using ehci-pci
[ 1214.870386] usb 2-1.2: device descriptor read/64, error -32
[ 1215.046264] usb 2-1.2: device descriptor read/64, error -32
[ 1215.222157] usb 2-1.2: new full-speed USB device number 85 using ehci-pci
[ 1215.629852] usb 2-1.2: device not accepting address 85, error -32
[ 1215.701801] usb 2-1.2: new full-speed USB device number 86 using ehci-pci
[ 1216.109511] usb 2-1.2: device not accepting address 86, error -32
[ 1216.109645] usb 2-1-port2: unable to enumerate USB device
[ 1217.316655] usb 2-1.2: new full-speed USB device number 87 using ehci-pci
[ 1217.388617] usb 2-1.2: device descriptor read/64, error -32
[ 1217.564480] usb 2-1.2: device descriptor read/64, error -32
[ 1217.740356] usb 2-1.2: new full-speed USB device number 88 using ehci-pci
[ 1217.812304] usb 2-1.2: device descriptor read/64, error -32
[ 1217.988179] usb 2-1.2: device descriptor read/64, error -32
[ 1218.164092] usb 2-1.2: new full-speed USB device number 89 using ehci-pci
[ 1218.571766] usb 2-1.2: device not accepting address 89, error -32
[ 1218.643718] usb 2-1.2: new full-speed USB device number 90 using ehci-pci
[ 1219.051426] usb 2-1.2: device not accepting address 90, error -32
[ 1219.051544] usb 2-1-port2: unable to enumerate USB device
[ 1220.258568] usb 2-1.2: new full-speed USB device number 91 using ehci-pci
[ 1220.330520] usb 2-1.2: device descriptor read/64, error -32
[ 1220.506395] usb 2-1.2: device descriptor read/64, error -32
[ 1220.682272] usb 2-1.2: new full-speed USB device number 92 using ehci-pci
[ 1220.754221] usb 2-1.2: device descriptor read/64, error -32
[ 1220.930095] usb 2-1.2: device descriptor read/64, error -32
[ 1221.105972] usb 2-1.2: new full-speed USB device number 93 using ehci-pci
[ 1221.513681] usb 2-1.2: device not accepting address 93, error -32
[ 1221.585632] usb 2-1.2: new full-speed USB device number 94 using ehci-pci
[ 1221.993340] usb 2-1.2: device not accepting address 94, error -32
[ 1221.993467] usb 2-1-port2: unable to enumerate USB device
[ 1222.153244] usb 2-1.2: new full-speed USB device number 95 using ehci-pci
[ 1222.225182] usb 2-1.2: device descriptor read/64, error -32
[ 1222.401065] usb 2-1.2: device descriptor read/64, error -32
[ 1222.576935] usb 2-1.2: new full-speed USB device number 96 using ehci-pci
[ 1222.648877] usb 2-1.2: device descriptor read/64, error -32
[ 1222.824755] usb 2-1.2: device descriptor read/64, error -32
[ 1223.000631] usb 2-1.2: new full-speed USB device number 97 using ehci-pci
[ 1223.408341] usb 2-1.2: device not accepting address 97, error -32
[ 1223.480293] usb 2-1.2: new full-speed USB device number 98 using ehci-pci
[ 1223.888013] usb 2-1.2: device not accepting address 98, error -32
[ 1223.888210] usb 2-1-port2: unable to enumerate USB device
[ 1224.035919] usb 2-1.2: new full-speed USB device number 99 using ehci-pci
[ 1224.107857] usb 2-1.2: device descriptor read/64, error -32
[ 1224.283717] usb 2-1.2: device descriptor read/64, error -32
[ 1224.459598] usb 2-1.2: new full-speed USB device number 100 using ehci-pci
[ 1224.531569] usb 2-1.2: device descriptor read/64, error -32
[ 1224.707428] usb 2-1.2: device descriptor read/64, error -32
[ 1224.883307] usb 2-1.2: new full-speed USB device number 101 using ehci-pci
[ 1225.291011] usb 2-1.2: device not accepting address 101, error -32
[ 1225.362968] usb 2-1.2: new full-speed USB device number 102 using ehci-pci
[ 1225.770678] usb 2-1.2: device not accepting address 102, error -32
[ 1225.770845] usb 2-1-port2: unable to enumerate USB device
[ 1225.918564] usb 2-1.2: new full-speed USB device number 103 using ehci-pci
[ 1225.990521] usb 2-1.2: device descriptor read/64, error -32
[ 1226.166422] usb 2-1.2: device descriptor read/64, error -32
[ 1226.342261] usb 2-1.2: new full-speed USB device number 104 using ehci-pci
[ 1226.414213] usb 2-1.2: device descriptor read/64, error -32
[ 1226.590097] usb 2-1.2: device descriptor read/64, error -32
[ 1226.765973] usb 2-1.2: new full-speed USB device number 105 using ehci-pci
[ 1227.173686] usb 2-1.2: device not accepting address 105, error -32
[ 1227.245623] usb 2-1.2: new full-speed USB device number 106 using ehci-pci
[ 1227.653336] usb 2-1.2: device not accepting address 106, error -32
[ 1227.653476] usb 2-1-port2: unable to enumerate USB device
[ 1228.860495] usb 2-1.2: new full-speed USB device number 107 using ehci-pci
[ 1228.932428] usb 2-1.2: device descriptor read/64, error -32
[ 1229.108301] usb 2-1.2: device descriptor read/64, error -32
[ 1229.284176] usb 2-1.2: new full-speed USB device number 108 using ehci-pci
[ 1229.356411] usb 2-1.2: device descriptor read/64, error -32
[ 1258.065448] usb 1-1.2: new full-speed USB device number 3 using ehci-pci
[ 1258.161085] usb 1-1.2: New USB device found, idVendor=03f0, idProduct=a407
[ 1258.161096] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1258.161103] usb 1-1.2: Product: HP Link-5 micro dongle
[ 1258.161108] usb 1-1.2: Manufacturer: HP
[ 1260.639298] usbcore: registered new interface driver usbhid
[ 1260.639302] usbhid: USB HID core driver
[ 1260.831272] input: HP HP Link-5 micro dongle as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:03F0:A407.0001/input/input27
[ 1260.831509] hid-generic 0003:03F0:A407.0001: input,hidraw0: USB HID v1.11 Keyboard [HP HP Link-5 micro dongle] on usb-0000:00:1a.0-1.2/input0
[ 1260.832833] input: HP HP Link-5 micro dongle as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:03F0:A407.0002/input/input28
[ 1260.836545] hid-generic 0003:03F0:A407.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [HP HP Link-5 micro dongle] on usb-0000:00:1a.0-1.2/input1
[ 2929.973387] usb 1-1.1: new full-speed USB device number 4 using ehci-pci
[ 2930.045335] usb 1-1.1: device descriptor read/64, error -32
[ 2930.221208] usb 1-1.1: device descriptor read/64, error -32
[ 2930.397092] usb 1-1.1: new full-speed USB device number 5 using ehci-pci
[ 2930.469042] usb 1-1.1: device descriptor read/64, error -32
[ 2930.644920] usb 1-1.1: device descriptor read/64, error -32
[ 2930.820792] usb 1-1.1: new full-speed USB device number 6 using ehci-pci
[ 2931.228497] usb 1-1.1: device not accepting address 6, error -32
[ 2931.300447] usb 1-1.1: new full-speed USB device number 7 using ehci-pci
[ 2931.708169] usb 1-1.1: device not accepting address 7, error -32
[ 2931.708373] usb 1-1-port1: unable to enumerate USB device
[ 5567.369375] usb 1-1.1: new full-speed USB device number 8 using ehci-pci
[ 5567.441321] usb 1-1.1: device descriptor read/64, error -32
[ 5567.617195] usb 1-1.1: device descriptor read/64, error -32
[ 5567.793070] usb 1-1.1: new full-speed USB device number 9 using ehci-pci
[ 5567.865020] usb 1-1.1: device descriptor read/64, error -32
[ 5568.040902] usb 1-1.1: device descriptor read/64, error -32
[ 5568.216771] usb 1-1.1: new full-speed USB device number 10 using ehci-pci
[ 5568.624480] usb 1-1.1: device not accepting address 10, error -32
[ 5568.696434] usb 1-1.1: new full-speed USB device number 11 using ehci-pci
[ 5569.104143] usb 1-1.1: device not accepting address 11, error -32
[ 5569.104221] usb 1-1-port1: unable to enumerate USB device
[ 5893.110604] usb 2-1.2: new low-speed USB device number 109 using ehci-pci
[ 5893.208644] usb 2-1.2: New USB device found, idVendor=046d, idProduct=c00e
[ 5893.208652] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5893.208657] usb 2-1.2: Product: USB-PS/2 Optical Mouse
[ 5893.208662] usb 2-1.2: Manufacturer: Logitech
[ 5893.212904] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:046D:C00E.0003/input/input41
[ 5893.213306] hid-generic 0003:046D:C00E.0003: input,hidraw2: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1.2/input0
[ 6003.083065] usb 1-1.2: USB disconnect, device number 3
[ 6003.480444] usb 1-1.1: new full-speed USB device number 12 using ehci-pci
[ 6003.552389] usb 1-1.1: device descriptor read/64, error -32
[ 6003.728255] usb 1-1.1: device descriptor read/64, error -32
[ 6003.904132] usb 1-1.1: new full-speed USB device number 13 using ehci-pci
[ 6003.976074] usb 1-1.1: device descriptor read/64, error -32
[ 6004.151955] usb 1-1.1: device descriptor read/64, error -32
[ 6004.327832] usb 1-1.1: new full-speed USB device number 14 using ehci-pci
[ 6004.735546] usb 1-1.1: device not accepting address 14, error -32
[ 6004.807497] usb 1-1.1: new full-speed USB device number 15 using ehci-pci
[ 6005.215194] usb 1-1.1: device not accepting address 15, error -32
[ 6005.215404] usb 1-1-port1: unable to enumerate USB device
Does it help or should i try an other command option?
Sorry to ask but i'm a lost.
Looks as if your USB port has some problems ...
Did you try on a different port yet?
Sent from my Nexus 7 using XDA-Developers mobile app
AndDiSa said:
Looks as if your USB port has some problems ...
Did you try on a different port yet?
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes i got 3 USB ports and i tried all of them :/
I think i will try on an other computer but i was wondering if it's not easier to use an old version of Windows (xp or 7) to get it work ?
Not really sure if that will help .. I am using a laptop with Ubuntu, too, and do not have any problems, but I am using always the USB 2.0 port because once I had problems connecting to a USB 3.0 port, too.
Sent from my Nexus 7 using XDA-Developers mobile app
I tried to plug the nexus 7 ( bootloader mode) to a windows 7/10 PC (without drivers installed) and i have exactly the same error on both os:
Is it normal ?
Thanks for your help.

Errors with SP Flash tools on Ubuntu 18.04

I have been trying to flash some old M2 Note units and so far I can't get the Preloader to talk over USB:
Code:
[ 1774.167123] usb 1-1: new high-speed USB device number 35 using xhci_hcd
[ 1774.320150] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[ 1774.320152] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1774.320153] usb 1-1: Product: MT65xx Preloader
[ 1774.320153] usb 1-1: Manufacturer: MediaTek
[ 1774.344085] cdc_acm 1-1:1.0: Zero length descriptor references
[ 1774.344093] cdc_acm: probe of 1-1:1.0 failed with error -22
[ 1774.384238] cdc_acm 1-1:1.1: ttyACM0: USB ACM device
[ 1776.971989] usb 1-1: USB disconnect, device number 35
I tried adding the vendor ID and product ID to the new_id of the cdc_acm driver and also masking/disabling the ModemManager service in case it was interfering.
I had the same issue on WIndows... it would reset immediately and kick into normal Android mode.
Anyone has any advice? I'm going to trying using the OTA zip with the modified/unlocked images for the preloader.
Flashing TWRP via Flashify did not work out.... rebooted into recovery to the default Meizu one.

Categories

Resources