First of all, as we all know, ZTE Blade V880 is an ancient phone. I did this just for fun.
My laptop is a 4th gen Intel platform (haswell), which has both EHCI and xHCI.
After plugging my Blade into the laptop, I found that fastboot cannot function. If it's plugged into the USB3.0 port, the device manager complained "code 10" (it was recognised as "Android Bootloader Interface" made by "Marshall London Device"), while it's plugged into the USB2.0 port, the error code was "code 43", with a message of "enumeration of BOS descriptor failed". (in this case it's just cataloged into abnormal USB device, lol)
After some googling (thanks to the code 43 actually!), I found that a registry hack of SkipBOSDescriptorQuery works. However, ironically, this fix only works on USB3.0 ports, which didn't throw "code 43" at all.
Steps:
1. Plug the phone into the USB3.0 port
2. Open the device manager, find out the hardware ID (vendor id and product id, aka VID and PID). For my Blade it was VID_18D1 PID_D00D REV_0100
3. Open regedit, locate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100 (see, it's [VID][PID][REV])
4. Create a DWORD value named "SkipBOSDescriptorQuery" and then change its value to 1
5. Done, just unplug and replug the USB cable once again, then it should work.
Related
I have noticed this morning that while my Xperia S is connected via USB cable to the PC it does not charge, ie. it indicates charging but battery level goes down rather than up. Also I've noticed that my OS (Fedora 16) stopped mounting Xperia's internal memory. Dmesg output is just that:
Code:
[34723.804074] usb 2-1.2: new full-speed USB device number 61 using ehci_hcd
[34723.877051] usb 2-1.2: device descriptor read/64, error -32
[34724.050920] usb 2-1.2: device descriptor read/64, error -32
[34724.224867] usb 2-1.2: new full-speed USB device number 62 using ehci_hcd
[34724.287808] usb 2-1.2: device descriptor read/64, error -32
[34724.461715] usb 2-1.2: device descriptor read/64, error -32
[34724.635655] usb 2-1.2: new full-speed USB device number 63 using ehci_hcd
[34725.037264] usb 2-1.2: device not accepting address 63, error -32
[34725.110414] usb 2-1.2: new full-speed USB device number 64 using ehci_hcd
[34725.512050] usb 2-1.2: device not accepting address 64, error -32
[34725.512180] hub 2-1:1.0: unable to enumerate USB device on port 2
Did a bit of research around the interwebs, found advice to clear data of the MtpApp app (settings -> applications -> all -> MtpApp), which I did but that didn't solve the problem, yet dmesg output changed a bit:
Code:
[34734.683275] usb 3-1: new full-speed USB device number 67 using xhci_hcd
[34734.686432] usb 3-1: Device not responding to set address.
[34734.890333] usb 3-1: Device not responding to set address.
[34735.091046] usb 3-1: device not accepting address 67, error -71
[34735.243993] usb 3-1: new full-speed USB device number 68 using xhci_hcd
[34735.247164] usb 3-1: Device not responding to set address.
[34735.451046] usb 3-1: Device not responding to set address.
[34735.651757] usb 3-1: device not accepting address 68, error -71
[34735.804727] usb 3-1: new full-speed USB device number 69 using xhci_hcd
[34735.807836] usb 3-1: Device not responding to set address.
[34736.011768] usb 3-1: Device not responding to set address.
[34736.212469] usb 3-1: device not accepting address 69, error -71
[34736.365416] usb 3-1: new full-speed USB device number 70 using xhci_hcd
[34736.368521] usb 3-1: Device not responding to set address.
[34736.572448] usb 3-1: Device not responding to set address.
[34736.773180] usb 3-1: device not accepting address 70, error -71
[34736.773208] hub 3-0:1.0: unable to enumerate USB device on port 1
Seems to also depend on the USB port I use in my laptop, ie. in one port it says "Device not responding", while on the other "device descriptor read/64, error -32". UPDATE: On double check it seems like USB 3.0 ports saying "not responding", while USB 2.0 port returns "descriptor error".
I obviously tried rebooting (including hard-reboot with volume-up key held), tried different cables, different PCs, including Windows one which just popped a balloon saying something about "unrecognized device". Nothing seems to rectify the issue. Needless to say it was working perfectly up until today.
Thankfully, it seems that's a software-related issue rather than physically borked USB port as I successfully managed to put device into flashmode (volume-up + usb plug). UPDATE: Unfortunately, even if physical plug to the port is recognized and green or blue light comes up, dmesg still returns "descriptor errors" and device is turning itself into charging-only mode (I initially thought just seeing blue/green light means either of modes is entered).
Running out of ideas what else I could do to get USB work again, apart from hard reset. Any suggestions more than welcome.
UPDATE: Out of the sudden, after 1525th reboot cycle somehow charging via USB cable works fine again, however internal storage is still not mounted to the PC. Doh! I guess I'll end up with warranty repair/replacement.
FINAL UPDATE: USB port died completely, plugging USB cable to the PC doesn't trigger any dmesg activity at all and handset after a while of doubt recognises connection as a standard wall charger. Sorting out warranty replacement as we speak.
Have you tried cleaning of the USB port/connector (of your phone)?
cognosco said:
Have you tried cleaning of the USB port/connector (of your phone)?
Click to expand...
Click to collapse
No, I haven't, but I doubt that's the case, as it wouldn't enter flashmode either.
Hi, suddenly (without any ROM flash attempt) my IAIWAI AW920 tablet got in a bootloop.
IIRC it's a RK3066 but the RKAndroidTool/Finn Flash Tool didn't recognized the tablet with either PWR Vol+ or PWR Vol- boot modes.
In the past I got the tablet successfully rooted through some tools, so in some past era I was able to communicate with ADB from the Android SDK (Linux Mint Kernel +3.10) but before it got soft-bricked I had not the USB debugging bridge set and due a failing HDD I lost that environment setup.
While being connected to my laptop through USB cable I can access two modes:
USB + PWR + Vol+: Blank black screen but I detect a USB device with VID: 10d6 PID: 10d6 that doesn't seems to be an adb client.
USB + PWR + Vol-: Appears a Fastboot kind of picture (Android mascot laying in the floor with his chest open and a Red Warning Symbol ) but no output whatsoever in [dmesg] or [udev monitor]
In neither these modes adb or fastboot detect something
---- For the Vol+ mode with the 10d6:10d6 device ----
I can't get adb or fastboot to work, even with adb_usb.ini edited in windows or linux or several different udev rules
The only udev rule I could trigger was
#IAIWAI
SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="10d6", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"
Click to expand...
Click to collapse
But it seems android_usb is not a link to a proper block device (the last number increases on each test)
ls -l /dev/
android_adb -> bus/usb/001/010
Click to expand...
Click to collapse
Or at least I can't make it work with
adb -p /dev/android_adb devices
or
fastboot -s /dev/android_adb devices
Extra information of the device found in Vol+ mode
lsusb:
Bus 001 Device 003: ID 10d6:10d6 Actions Semiconductor Co., Ltd
dmesg:
[11102.331560] usb 1-2: new high-speed USB device number 10 using ehci-pci
[11102.464620] usb 1-2: New USB device found, idVendor=10d6, idProduct=10d6
[11102.464633] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
udevadm monitor:
KERNEL[8596.157794] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
KERNEL[8596.158995] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
UDEV [8596.167280] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
UDEV [8596.171388] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
P: /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVTYPE=usb_interface
E: ID_VENDOR_FROM_DATABASE=Actions Semiconductor Co., Ltd
E: INTERFACE=255/255/255
E: MODALIAS=usb:v10D6p10D6d0100dc00dsc00dp00icFFiscFFipFFin00
E: PRODUCT=10d6/10d6/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: USEC_INITIALIZED=434099056
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 --attribute-walk:
looking at device '/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0':
KERNEL=="1-2:1.0"
SUBSYSTEM=="usb"
DRIVER==""
ATTR{bInterfaceClass}=="ff"
ATTR{bInterfaceSubClass}=="ff"
ATTR{bInterfaceProtocol}=="ff"
ATTR{bNumEndpoints}=="02"
ATTR{supports_autosuspend}=="1"
ATTR{bAlternateSetting}==" 0"
ATTR{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1/1-2':
KERNELS=="1-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="2"
ATTRS{idVendor}=="10d6"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="4"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="128mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="6"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="10d6"
ATTRS{bDeviceClass}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="5"
ATTRS{bcdDevice}=="0313"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:12.2"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="91"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.13.0-37-generic ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:12.2':
KERNELS=="0000:00:12.2"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="17"
ATTRS{subsystem_vendor}=="0x1179"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{enabled}=="1"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
ATTRS{device}=="0x4396"
ATTRS{uframe_periodic_max}=="100"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-1"
ATTRS{vendor}=="0x1002"
ATTRS{subsystem_device}=="0xff1e"
ATTRS{numa_node}=="0"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
Click to expand...
Click to collapse
Hi guys,
I'm trying to get my old DNA hooked up to my PC to recover a couple of file. The issue that I'm having at the moment is that I can't seem to get it to turn on. I've tried charging it with both a wall and wireless charging and neither one gives me any lights on the device at all. No orange power light, no red blinking error lights, just nothing. I've tried to pull it apart and remove and reseat the power ribbon, but that did nothing for me either. When I plug it into the PC it gives me some noises like it recognizes the device, but it doesn't map the drive like I would hope. To compound the issue further, I had issues with the power button long before I stopped using the device, so I'm not sure if when I'm holding it down it's actually doing anything. Below is the info I'm able to obtain from the device when it's plugged into the PC. Any ideas on how I could use this to perform a back up? It looks to me like it's trying to connect via serial, but not sure if this is beneficial or detrimental, or just wrong.
HTML isn't work, so lets try a list I suppose.
Device Name: QHSUSB_DLOAD
Description: RELINK HS-USB QDLoader 9008
Device Type: Vendor Specific
Connected: Yes
Safe to Unplug: Yes
Disabled: No
USB Hub: No
Drive Letter: COM4
Serial Number:
Created Date: 9/12/2016 2:12:36 PM
Last Plug/Unplug Date: 9/12/2016 2:42:39 PM
VedorID: 05c6
ProductID: 9008
Firmware Revision: 0.00
USB Class: ff
USB SubClass: ff
USB Protocol: ff
Service Name: cmnxusbser
Service Description: Mobile Connector USB Device for Legacy Serial Communication LCT2053s 20140303
Driver Filename: cmnxusbser.sys
Device Class: Ports
Device MFG: Mobile Connector
Power: 2 mA
USB Version: 2.00
Driver Description: RELINK HS-USB QDLoader 9008
Driver Version: 2.1.0.3
Driver InfSection: CMNSportInstall00
Driver InfPath: oem89.inf
Instance ID: USB\VID_05C6&PID_9008\5&3acdd96d&0&1
Capabilities: SurpriseRemovalOK
HTML:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html><head><title>USB Devices List</title></head>
<body>
<h3>USB Devices List</h3>
<br><h4>link to nirsoft was here, XDA won't let it post though.
<th>Device Name
<th>Description
<th>Device Type
<th>Connected
<th>Safe To Unplug
<th>Disabled
<th>USB Hub
<th>Drive Letter
<th>Serial Number
<th>Created Date
<th>Last Plug/Unplug Date
<th>VendorID
<th>ProductID
<th>Firmware Revision
<th>USB Class
<th>USB SubClass
<th>USB Protocol
<th>Hub / Port
<th>Computer Name
<th>Vendor Name
<th>Product Name
<th>ParentId Prefix
<th>Service Name
<th>Service Description
<th>Driver Filename
<th>Device Class
<th>Device Mfg
<th>Power
<th>USB Version
<th>Driver Description
<th>Driver Version
<th>Driver InfSection
<th>Driver InfPath
<th>Instance ID
<th>Capabilities
<tr><td bgcolor=#FFFFF0 nowrap>QHSUSB_DLOAD<td bgcolor=#FFFEF0 nowrap>RELINK HS-USB QDLoader 9008<td bgcolor=#FFFDF0 nowrap>Vendor Specific<td bgcolor=#FFFCF0 nowrap>Yes<td bgcolor=#FFFBF0 nowrap>Yes<td bgcolor=#FFFAF0 nowrap>No<td bgcolor=#FFF9F0 nowrap>No<td bgcolor=#FFF8F0 nowrap>COM4<td bgcolor=#FFF7F0 nowrap> <td bgcolor=#FFF7F0 nowrap>9/12/2016 2:12:36 PM<td bgcolor=#FFF6F0 nowrap>9/12/2016 2:42:39 PM<td bgcolor=#FFF5F0 nowrap>05c6<td bgcolor=#FFF4F0 nowrap>9008<td bgcolor=#FFF3F0 nowrap>0.00<td bgcolor=#FFF2F0 nowrap>ff<td bgcolor=#FFF1F0 nowrap>ff<td bgcolor=#FFF0F0 nowrap>ff<td bgcolor=#FFF0F0 nowrap> <td bgcolor=#FEF0F0 nowrap> <td bgcolor=#FDF0F1 nowrap> <td bgcolor=#FCF0F2 nowrap> <td bgcolor=#FBF0F3 nowrap> <td bgcolor=#FAF0F4 nowrap>cmnxusbser<td bgcolor=#F9F0F5 nowrap>Mobile Connector USB Device for Legacy Serial Communication LCT2053s 20140303<td bgcolor=#F8F0F6 nowrap>cmnxusbser.sys<td bgcolor=#F7F0F7 nowrap>Ports<td bgcolor=#F7F0F7 nowrap>Mobile Connector<td bgcolor=#F6F0F8 nowrap>2 mA<td bgcolor=#F5F0F9 nowrap>2.00<td bgcolor=#F4F0FA nowrap>RELINK HS-USB QDLoader 9008<td bgcolor=#F3F0FB nowrap>2.1.0.3<td bgcolor=#F2F0FC nowrap>CMNSportInstall00<td bgcolor=#F1F0FD nowrap>oem89.inf<td bgcolor=#F0F0FE nowrap>USB\VID_05C6&PID_9008\5&3acdd96d&0&1<td bgcolor=#F0F0FF nowrap>SurpriseRemovalOK
</table>
</body></html>
Any Help is greatly appreciated.
I am trying to root a Lava Z60 phone, for which I try to enter fastboot mode. Using either "adb reboot bootloader" or powerbutton + volume up and selecting fastboot, I get to a blank screen. The device ID in USB changes to a different one from that of adb. I can see the device in dmesg as:
Code:
[30482.597989] usb 2-1.1: new high-speed USB device number 53 using ehci-pci
[30482.707638] usb 2-1.1: New USB device found, idVendor=0e8d, idProduct=20ff
[30482.707643] usb 2-1.1: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[30482.707646] usb 2-1.1: Product: Android
[30482.707649] usb 2-1.1: Manufacturer: Android
[30482.707652] usb 2-1.1: SerialNumber: 0123456789ABCDEF
But when I run "fastboot devices" the result is empty ( I tested on Linux, windows and FreeBSD). To debug I downloaded the python version of adb and fastboot tools and put in some print statements for the data sent to the phone and returned by it . The library expects these values(settings) to be returned from the device in fastboot mode(they are hardcoded):
class = 0xff, subclass = 0x42, protocol = 0x03
Instead my phone returns:
class = 0x03, subclass = 0x00, protocol = 0x00
I tried changing the hardcoded values to the ones returned by the phone but it resulted in a USB error. So I think my phone is not properly entering fastboot mode. Why could that be, and how can it be fixed?
N30xda said:
I am trying to root a Lava Z60 phone, for which I try to enter fastboot mode..........
Click to expand...
Click to collapse
I don't have this device myself but, your best bet would be to check out one of the following Guides regarding Fastboot.
https://forum.xda-developers.com/showthread.php?t=3239537
https://forum.xda-developers.com/showthread.php?t=2277112
There's other similar Guides/Tutorials on the forum but, those should give you a good start for what you are looking to do. Don't be afraid to ask for some member guidance within one of them too.
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
How can i update my lava z 60 into android q pls tell
ASHOKJAIN said:
How can i update my lava z 60 into android q pls tell
Click to expand...
Click to collapse
Don't think stock Android Q firmware is available for this device. If available then you've to use SP Flash Tool in order to install it.
I'm having problems with a Chinese tablet that I believe to be a Mediatek TAB910 with a MTK6592 processor.
It started by having problems with the SIM slots which I put down to a faulty SIM card. I obtained another from the telco but that didn't solve the problem. I concluded that the problem was with the SIM slots or with the software so I did a factory reset.
That appears to have gone well EXCEPT that I cannot get past the "Enter Privacy Protection password" screen (PPP). Let me say at this stage that I have never used PINs on my SIM cards; in fact, if I put a SIM card in which has a PIN then the screen asks for and accepts the SIM PIN but still presents the PPP screen.
I have tried to connect to the tablet by USB in order to try SP FLASH, but that tool doesn't see the tablet at all.
I then tried sudo dmesg|grep usb to see if there was any recognition of the USB and got the following results:
[237820.461318] usb 1-2: new high-speed USB device number 22 using xhci_hcd
[237820.611762] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[237820.611773] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[237820.611779] usb 1-2: Product: MT65xx Preloader
[237820.611783] usb 1-2: Manufacturer: MediaTek
[237823.266112] usb 1-2: USB disconnect, device number 22
[237830.885144] usb 1-2: new high-speed USB device number 23 using xhci_hcd
[237831.034440] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2002, bcdDevice=ff.ff
[237831.034451] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[237831.034456] usb 1-2: Product: TAB910
[237831.034461] usb 1-2: Manufacturer: MediaTek
[237831.034465] usb 1-2: SerialNumber: 0123456789ABCDEF
[237831.038098] usb-storage 1-2:1.0: USB Mass Storage device detected
[237831.045186] scsi host2: usb-storage 1-2:1.0
[237831.471860] usb 1-2: USB disconnect, device number 23
Click to expand...
Click to collapse
It appears that the tablet is identifying itself, but immediately disconnecting again, hence no response from SP FLASH.
I can get the tablet to drop into two factory setting levels, one with English language instructions, the other with Chinese language instructions. Both of these appear to work as expected when I run through the menu items including, in the Chinese menu, "Eliminate eMMC".
I have also modified the udev files, but seemingly to no avail.
~$ cat /etc/udev/rules.d/80-persistent-usb.rules
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2000“
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2002“
~$ sudo service udev restart
Click to expand...
Click to collapse
My question is: Where do I go from here before I decide to bin this chablet.
TIA
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
James_Watson said:
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
Click to expand...
Click to collapse
Thanks for that but I have already been down that rabbit hole without success. My big problem is that the USB comes up but promptly disconnects again
Usually MTk preloader comport will disconnect if correct bootloader is not detected. So check you've got MTK6592 supported sp flashtool version and original firmware loaded. For privacy protection removal you need to format whole flash except bootloader and flash origin firmware then need to repair imei.
For some models you need to press and hold VOL+ or VOL- or both to get in to flash mode.