El 22 de septiembre de 2017 21:39:10 CEST, Denis 'GNUtoo' Carikli <[email protected]> escribió: >Hi, > >I'm not sure where the problem comes from, so I prefer asking on the >mailing list rather than doing a bug report. > >With the i3900, I am able to use heimdall to reflash the recovery: >> # dmesg >> [...] >> [ 4427.133539] usb 1-1: USB disconnect, device number 2 >> [ 4429.400157] usb 1-1: new high-speed USB device number 3 using >> ehci-pci [ 4429.668691] usbcore: registered new interface driver >> cdc_acm [ 4429.668699] cdc_acm: USB Abstract Control Model driver for >> USB modems and ISDN adapters # heimdall flash --RECOVERY >> recovery-i9300.img Heimdall v1.4.2 >> >> Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna >> http://www.glassechidna.com.au/ >> >> This software is provided free of charge. Copying and redistribution >> is encouraged. >> >> If you appreciate this software and you would like to support future >> development please consider donating: >> http://www.glassechidna.com.au/donate/ >> >> Initialising connection... >> Detecting device... >> libusb: error [_get_usbfs_fd] libusb couldn't open USB >> device /dev/bus/usb/001/003: Input/output error ERROR: Failed to >> access device. libusb error: -1 # heimdall flash --RECOVERY >> recovery-i9300.img Heimdall v1.4.2 >> >> Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna >> http://www.glassechidna.com.au/ >> >> This software is provided free of charge. Copying and redistribution >> is encouraged. >> >> If you appreciate this software and you would like to support future >> development please consider donating: >> http://www.glassechidna.com.au/donate/ >> >> Initialising connection... >> Detecting device... >> Claiming interface... >> Setting up interface... >> >> Initialising protocol... >> Protocol initialisation successful. >> >> Beginning session... >> >> Some devices may take up to 2 minutes to respond. >> Please be patient! >> >> Session begun. >> >> Downloading device's PIT file... >> PIT file download successful. >> >> Uploading RECOVERY >> 100% >> RECOVERY upload successful >> >> Ending session... >> Rebooting device... >> Releasing device interface... > >Here It successfully flashed the new recovery. > >Here's the heimdall version I have: >> # pacman -sS heimdall >> community/heimdall 1.4.2-1 [installed] >> Tool suite used to flash firmware (aka ROMs) onto Samsung mobile >> devices > >Then after booting, I look again at dmesg: >> [ 4447.083519] usb 1-1: reset high-speed USB device number 3 using >> ehci-pci [ 4447.222649] usb 1-1: USB disconnect, device number 3 >> [ 4447.343381] usb 1-1: new high-speed USB device number 4 using >> ehci-pci [ 4454.678355] usb 1-1: USB disconnect, device number 4 >> [ 4477.980152] usb 1-1: new high-speed USB device number 5 using >> ehci-pci >and it tells me that there are new devices on the USB bus, with the >device number increasing. > >After that I try to connect to it trough adb: >> # adb shell >> * daemon not running. starting it now at tcp:5037 * >> * daemon started successfully * >> error: no devices/emulators found >and it founds no device. > >And after that, my laptop's kernel sees many new USB devices, and the >number is still increasing constantly: >> [ 4660.770129] usb 1-1: new high-speed USB device number 10 using >> ehci-pci [ 4661.133406] usb 1-1: reset high-speed USB device number >> 10 using ehci-pci [ 4661.271740] usb 1-1: USB disconnect, device >> number 10 [ 4661.526741] usb 1-1: new high-speed USB device number 11 >> using ehci-pci [ 4661.890054] usb 1-1: reset high-speed USB device >> number 11 using ehci-pci [ 4662.028246] usb 1-1: USB disconnect, >> device number 11 [ 4662.280105] usb 1-1: new high-speed USB device >> number 12 using ehci-pci [ 4662.653407] usb 1-1: reset high-speed USB >> device number 12 using ehci-pci [ 4662.791001] usb 1-1: USB >> disconnect, device number 12 > >For instance after a some time I get: >> [ 4865.423432] usb 1-1: new high-speed USB device number 27 using >> ehci-pci [ 4865.793348] usb 1-1: reset high-speed USB device number >> 27 using ehci-pci [ 4865.931646] usb 1-1: USB disconnect, device >> number 27 [ 4866.186783] usb 1-1: new high-speed USB device number 28 >> using ehci-pci [ 4866.550053] usb 1-1: reset high-speed USB device >> number 28 using ehci-pci [ 4866.687673] usb 1-1: USB disconnect, >> device number 28 > >After a reboot I then get some: >> [ 5070.283389] usb 1-1: reset high-speed USB device number 13 using >> ehci-pci [ 5070.425048] usb 1-1: can't restore configuration #1 >> (error=-71) [ 5070.425283] usb 1-1: USB disconnect, device number 13 >> [ 5070.680067] usb 1-1: new high-speed USB device number 14 using >> ehci-pci [ 5071.043499] usb 1-1: reset high-speed USB device number >> 14 using ehci-pci [ 5071.191739] usb 1-1: can't restore configuration >> #1 (error=-71) [ 5071.191990] usb 1-1: USB disconnect, device number >> 14 [ 5071.443423] usb 1-1: new high-speed USB device number 15 using >> ehci-pci [ 5071.556739] usb 1-1: device descriptor read/64, error -32 >> [ 5071.776704] usb 1-1: device descriptor read/64, error -32 >> [ 5071.996735] usb 1-1: new high-speed USB device number 16 using >> ehci-pci [ 5072.110085] usb 1-1: device descriptor read/64, error -32 >> [ 5072.330093] usb 1-1: device descriptor read/64, error -32 > >Questions: >- Are other people getting similar behavior?
I've had similar behavior with bad USB cables or connectors (wether in the phone or in the computer). HTH Best regards >- Can it be related to USB power management? I've deactivated USB bus > power management but it didn't fix the issue. > >I can also try to deactivate more power management and/or try other >computers to try to narrow down the issue. > >Denis. Laura Arjona Reina https://wiki.debian.org/LauraArjona _______________________________________________ Replicant mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/replicant
