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.
Related
Hi,
I recently acquired a TF101 and I am trying to do some development on it.
I have USB debugging on and tried to put it in APX mode by powering up using vol + and power button. It is connected to laptop running ubuntu 12.04 and I see following kernel messages
[ 3650.272049] usb 3-1: new low-speed USB device number 38 using ohci_hcd
[ 3650.452045] usb 3-1: device descriptor read/64, error -62
[ 3650.736044] usb 3-1: device descriptor read/64, error -62
[ 3651.016046] usb 3-1: new low-speed USB device number 39 using ohci_hcd
[ 3651.196038] usb 3-1: device descriptor read/64, error -62
[ 3651.484049] usb 3-1: device descriptor read/64, error -62
[ 3651.764103] usb 3-1: new low-speed USB device number 40 using ohci_hcd
[ 3652.172100] usb 3-1: device not accepting address 40, error -62
[ 3652.348103] usb 3-1: new low-speed USB device number 41 using ohci_hcd
[ 3652.756046] usb 3-1: device not accepting address 41, error -62
[ 3652.756060] hub 3-0:1.0: unable to enumerate USB device on port 1
any suggesstions ?
viewlessguru said:
Hi,
I recently acquired a TF101 and I am trying to do some development on it.
I have USB debugging on and tried to put it in APX mode by powering up using vol + and power button. It is connected to laptop running ubuntu 12.04 and I see following kernel messages
[ 3650.272049] usb 3-1: new low-speed USB device number 38 using ohci_hcd
[ 3650.452045] usb 3-1: device descriptor read/64, error -62
[ 3650.736044] usb 3-1: device descriptor read/64, error -62
[ 3651.016046] usb 3-1: new low-speed USB device number 39 using ohci_hcd
[ 3651.196038] usb 3-1: device descriptor read/64, error -62
[ 3651.484049] usb 3-1: device descriptor read/64, error -62
[ 3651.764103] usb 3-1: new low-speed USB device number 40 using ohci_hcd
[ 3652.172100] usb 3-1: device not accepting address 40, error -62
[ 3652.348103] usb 3-1: new low-speed USB device number 41 using ohci_hcd
[ 3652.756046] usb 3-1: device not accepting address 41, error -62
[ 3652.756060] hub 3-0:1.0: unable to enumerate USB device on port 1
any suggesstions ?
Click to expand...
Click to collapse
If your using USB 3.0 ports to connect the tablet try switching to a usb 2.0 port. usb3 has been known to cause add issues sometimes.
Try each of your USB ports. I have issues with my tablet not being seen on all but one port on my PC. Even though stuff works in the other ports It still was not seen.
Sent from my Transformer TF101 using xda premium
What do you see on "$lsusb"?
Can you see an Nvidia Device?
So I currently am running ubuntu 15 and another computer with mint 17.
ON both computers I have tried heimdall and Jodin. Both have been unable to obtain a pit file. I get that error -7 which appears to be something related to not receiving any packets back from the phone.
When I connect the phone outside of download mode - adb works also
$Dmesg | tail
[email protected]:~$ dmesg | tail
[ 2663.619751] cdc_acm 3-1.1:1.1: failed to set dtr/rts
[ 2663.691610] cdc_acm 3-1.1:1.1: ttyACM2: USB ACM device
[ 2663.693138] usb 3-1.1: USB disconnect, device number 7
[ 2663.911119] usb 3-1.1: new high-speed USB device number 8 using ehci-pci
[ 2664.021218] usb 3-1.1: New USB device found, idVendor=04e8, idProduct=6860
[ 2664.021231] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2664.021238] usb 3-1.1: Product: SAMSUNG_Android
[ 2664.021245] usb 3-1.1: Manufacturer: SAMSUNG
[ 2664.021250] usb 3-1.1: SerialNumber: 4b6bda34
[ 2664.023462] cdc_acm 3-1.1:1.1: ttyACM2: USB ACM device
[email protected]:~$ adb devices
List of devices attached
4b6bda34 device
In download mode...$dmesg | tail
[email protected]:~$ dmesg | tail
1062.584521] usb 3-1.1: new high-speed USB device number 3 using ehci-pci
[ 1062.693317] usb 3-1.1: New USB device found, idVendor=04e8, idProduct=685d
[ 1062.693328] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1062.693334] usb 3-1.1: Product: MSM8960
[ 1062.693339] usb 3-1.1: Manufacturer: Sasmsung
[ 1062.807263] cdc_acm 3-1.1:1.0: ttyACM0: USB ACM device
[ 1062.807597] usbcore: registered new interface driver cdc_acm
[ 1062.807601] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[email protected]:~$ adb devices
List of devices attached
Not quite sure what to make of this. Especally the spelling of "Samsung" ...the product doesn't match. I don't know why its showing as a CDC_ACM modem. I was toying with the idea of blacklisting it again. But I tried that on my mint distro and it had no effect. ADB also shows no devices but Heimdall detects it. Fastboot also shows no devices during download mode. I'm kind of stuck here. Not sure how to fix this error.
-All drivers are installed
- 51 rules don't fix it
-blacklisting cdc doesn't work
-swapping doesn't work
Anyone have any ideas?
?
http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
USB debugging on Linux
Maybe it's just me being blind, but does anyone have `adb` working on Linux? Device ID shows up as 0fca, and I've added this to my udev rules, but still no device. Notification shows "USB debugging connected - Touch to disable USB debugging" with "Media device (MTP)" and "Camera (PTP)" USB connections.
Code:
07:32:04 ~$ lsusb |grep Research
Bus 001 Device 003: ID 0fca:8032 Research In Motion, Ltd.
Code:
[ 397.648593] usb 1-1: new high-speed USB device number 3 using ehci-pci
[ 397.920791] usb 1-1: New USB device found, idVendor=0fca, idProduct=8032
[ 397.920796] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 397.920798] usb 1-1: Product: BlackBerry
[ 397.920799] usb 1-1: Manufacturer: BlackBerry
[ 397.920801] usb 1-1: SerialNumber: <x>
Code:
07:39:49 ~$ adb devices
List of devices attached
Thanks!
Figured it out. My Linux environment (Ubuntu 14) had the package 'android-tools-adb' installed, but that version of `adb` doesn't seem to work. The `adb` binary with the SDK tools works fine. I removed the 'android-tools-adb' and all is well again. :laugh:
Hi,
I am attaching USB to my Ubuntu 14.04 but getting following logs. Looks like USB-C type is not supported on Ubuntu. Could you please guide me how to enable, or any driver?
lsusb logs:
Code:
[ 127.987537] usb 1-1.1: new high-speed USB device number 5 using ehci-pci
[ 128.081611] usb 1-1.1: New USB device found, idVendor=2b0e, idProduct=1714
[ 128.081622] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 128.081627] usb 1-1.1: Product: Android
[ 128.081631] usb 1-1.1: Manufacturer: Android
[ 128.081635] usb 1-1.1: SerialNumber: 57638e68
[ 146.986991] usb 1-1.1: USB disconnect, device number 5
[ 147.184969] usb 1-1.1: new high-speed USB device number 6 using ehci-pci
[ 147.279176] usb 1-1.1: New USB device found, idVendor=2b0e, idProduct=1714
[ 147.279184] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 147.279187] usb 1-1.1: Product: Android
[ 147.279190] usb 1-1.1: Manufacturer: Android
[ 147.279193] usb 1-1.1: SerialNumber: 57638e68
Adb devices:
Code:
adb devices
List of devices attached
I'm using Debian 8.8 and it works fine for me. Try updating your system. Ubuntu 17 is out now.
Sent from my X526 using Tapatalk
Does it work with 'sudo'?
[SOLVED] Used the guide here for EDL mode and back up. https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543
Went to restore my OrangeFox backup, everything seemed well, so I rebooted.. nothing, no bootlogo, but the screen is lit. Ok, try fastboot, hold powerbutton down for 12 seconds, rebooted (vibrated), hold volume up and power.. no fast boot.. I hope I haven't borked something, can't get into fastboot or recovery. screen is black, no boot logo, nothing but screen is lit. nothing shows up on adb devices while at the black screen.
Before backup restored, USB Plugged in looked like this:
[ 2532.267203] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2532.267204] usb 4-5: Product: SDM660-MTP _SN:50B88856
[ 2532.267205] usb 4-5: Manufacturer: Xiaomi
[ 2532.267206] usb 4-5: SerialNumber: ********
[ 2732.465636] usb 4-5: USB disconnect, device number 12
[ 2743.383822] usb 4-5: new high-speed USB device number 13 using ehci-pci
[ 2743.513131] usb 4-5: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 2.23
Click to expand...
Click to collapse
Now it looks like this
6395.629532] usb 4-5: new high-speed USB device number 24 using ehci-pci
[ 6395.758655] usb 4-5: New USB device found, idVendor=18d1, idProduct=d00d, bcdDevice= 1.00
[ 6395.758658] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6395.758660] usb 4-5: Product: Android
[ 6395.758661] usb 4-5: Manufacturer: Google
[ 6395.758662] usb 4-5: SerialNumber: ********
Click to expand...
Click to collapse
Ok, I see, EDL mode it is.. https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543