Database Develop

USB and PC Charging Drivers

Motorola USB Drivers (for Windows®)
This USB Driver is used for connecting your Motorola Mobile Device or tablet to a Windows® computer via a USB cable in order for the computer to recognize the device.
Supported Products
This USB Driver supports most Motorola Android, Motorola OS, Motorola Linux OS, Motorola iDEN, Motorola Symbian/UIQ, Motorola Windows Mobile® and Motorola i-mode devices. In addition, this USB driver now supports the Motorola XOOM™ tablet.
System Requirements
A 32-bit or 64-bit version of Windows 2000®, Windows XP®, Windows Vista® or Windows 7® Operating system.
You must have Administrator permission to install this driver.
Notes
We recommend you reboot the system after installing the USB Driver.
Download Motorola 5.4.0 Driver with MotoHelper here
Click to expand...
Click to collapse

Wait, does the phone not just change normally when connected? I have never had an issue with that on my old phones...

[Q] Kindle fire HD 7" not recognised as an MTP device anymore

I have a Kinde fire HD 7" that I rooted for a neighbours son which he managed to brick within 20 Mins of getting it back, I think the battery died on him when he was installing something. Now when I plug the Kindle into my system which runs Linux I get the following in the logs.
Feb 13 15:01:05 kernel: [ 161.419037] usb 1-5: new high speed USB device using ehci_hcd and address 5
Feb 13 15:01:05 kernel: [ 161.533760] usb 1-5: New USB device found, idVendor=0451, idProduct=d010
Feb 13 15:01:05 kernel: [ 161.533767] usb 1-5: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 13 15:01:05 kernel: [ 161.533772] usb 1-5: Product: OMAP4440
Feb 13 15:01:05 kernel: [ 161.533775] usb 1-5: Manufacturer: Texas Instruments
Feb 13 15:01:05 mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Feb 13 15:01:05 mtp-probe: bus: 1, device: 5 was not an MTP device
Feb 13 15:01:08 kernel: [ 164.534204] usb 1-5: USB disconnect, address 5
Feb 13 15:01:08 kernel: [ 165.305041] usb 1-5: new high speed USB device using ehci_hcd and address 6
Feb 13 15:01:09 kernel: [ 165.419856] usb 1-5: New USB device found, idVendor=0451, idProduct=d010
Feb 13 15:01:09 kernel: [ 165.419863] usb 1-5: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 13 15:01:09 kernel: [ 165.419868] usb 1-5: Product: OMAP4440
Feb 13 15:01:09 kernel: [ 165.419871] usb 1-5: Manufacturer: Texas Instruments
Feb 13 15:01:09 mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Feb 13 15:01:09 mtp-probe: bus: 1, device: 6 was not an MTP device
Feb 13 15:01:12 kernel: [ 168.420300] usb 1-5: USB disconnect, address 6`
Click to expand...
Click to collapse
This repeats ad infinitum, well at least 30 times I unplugged it after that.
My question is this, will I be able to to restore the Kindle using the Factory cable from SkOrPn or is this a case where I need to send it back to Amazon ??
Any help would be much appreciated.

JBDegriz said:
I have a Kinde fire HD 7" that I rooted for a neighbours son which he managed to brick within 20 Mins of getting it back, I think the battery died on him when he was installing something. Now when I plug the Kindle into my system which runs Linux I get the following in the logs.
This repeats ad infinitum, well at least 30 times I unplugged it after that.
My question is this, will I be able to to restore the Kindle using the Factory cable from SkOrPn or is this a case where I need to send it back to Amazon ??
Any help would be much appreciated.
Click to expand...
Click to collapse
Is the device still able to comunicate with ADB? If it can then you do not need a fastboot cable. If it does not then yes you will need one to restore it..

lacoursiere18 said:
Is the device still able to comunicate with ADB? If it can then you do not need a fastboot cable. If it does not then yes you will need one to restore it..
Click to expand...
Click to collapse
No ADB never sees the device any more as the USB just keeps reconnecting and disconnecting. The same thing happens in windows where I keep getting the sound when you connect a usb device over and over again and windows looks for a device driver for an OMAP4440, which I believe is the CPU in the Kindle.
So I need to know that in a situation like this that the Factory cable would actually help, I'm sure I read somewhere that fastboot mode needs a working bootloader and I'm not sure that this kindles bootloader is still there.
Thanks

JBDegriz said:
No ADB never sees the device any more as the USB just keeps reconnecting and disconnecting. The same thing happens in windows where I keep getting the sound when you connect a usb device over and over again and windows looks for a device driver for an OMAP4440, which I believe is the CPU in the Kindle.
So I need to know that in a situation like this that the Factory cable would actually help, I'm sure I read somewhere that fastboot mode needs a working bootloader and I'm not sure that this kindles bootloader is still there.
Thanks
Click to expand...
Click to collapse
Yea it doesn't sound like it's in working order, so yes, a fastboot cable would be need to get the device back in action..

Hi, I have the same problem, did you manage to cure it with the skorn cable, I am asking because I have made a factory cable myself but its giving the same problem.
lacoursiere18 said:
Yea it doesn't sound like it's in working order, so yes, a fastboot cable would be need to get the device back in action..
Click to expand...
Click to collapse

devilxmax said:
Hi, I have the same problem, did you manage to cure it with the skorn cable, I am asking because I have made a factory cable myself but its giving the same problem.
Click to expand...
Click to collapse
No I'm afraid not. If your device is being recognised as an OMAP4440 then your out of luck as there are no drivers for this yet. I had to send my device back to Amazon who replaced it no questions asked.
A good thread to check is http://forum.xda-developers.com/showthread.php?t=2096888 post a few details of your problem on that thread and you will get a helpful response.
Good luck

OxygenOS install bricked my phone (and there are no Windows machines around)

I think I've managed to successfully brick my phone through the following process...
1. boot into recovery
2. enable sideload mode
3. adb sideload the OxygenOS beta 9 image (downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/)
Everything went smoothly and the sideload process finished successfully. Rebooted the phone, wandered away for a bit...and now it's just a black screen that won't turn on. Plugging it into my laptop I see that is identifying itself as a QUSB__BULK device:
Code:
usb 1-1.4.4: new high-speed USB device number 18 using xhci_hcd
usb 1-1.4.4: New USB device found, idVendor=05c6, idProduct=9008
usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4.4: Product: QUSB__BULK
usb 1-1.4.4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 1-1.4.4:1.0: Qualcomm USB modem converter detected
usb 1-1.4.4: Qualcomm USB modem converter now attached to ttyUSB0
What are my options at this point? All of the recovery guides I've been able to find so far start by downloading some Windows utilities, and I don't have easy access to a Windows machine.

Use the Hard Brick guide, download the full tool unbrick guide and it should work fine, follow method 2. you can find hard unbrick guide on google.

Unfortunately, the hard unbrick guide (if you mean forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/) seems to be Windows-only (it has instructions for downloading lots of Windows device drivers, etc), and as I said in my original question, I don't have a Windows machine handy.

So I have not looked alot around but I haven't seen any guides or something for Linux, but 2 ideas:
1: try that guide, maybe Linux won't need the drivers and it would work just fine.
2: you can download a windows image, install it on a Virtual Machine,unbrick your phone and then delete the VM and everything.

Is your phone's bootloader unlocked? If yes, things will much more simple.
anyway, try download full 3.2.8 ROM from OP site, boot your phone to fastboot mode and sideload it.

I'm pretty sure I bricked my phone bad...

I was trying to reflash the system ROM, and accidentally canceled the ./flash_all script... Now, when I connect my phone, dmesg -w running on my host (Arch Linux) returns this:
HTML:
[22650.389556] usb 3-1.3: new high-speed USB device number 73 using xhci_hcd
[22650.485540] usb 3-1.3: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
[22650.485542] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[22650.485543] usb 3-1.3: Product: QUSB_BULK_CID:0402_SN:301E7E84
[22650.485544] usb 3-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[22650.492441] qcserial 3-1.3:1.0: Qualcomm USB modem converter detected
[22650.492528] usb 3-1.3: Qualcomm USB modem converter now attached to ttyUSB0

Update: So I've discovered now that my phone is apparently in Qualcomm's QDL, or Emergency Download mode... I found a tool here that apparently allows you to flash an image to a device running in this mode...

Were you able to unbrick your phone?

peneoark said:
Were you able to unbrick your phone?
Click to expand...
Click to collapse
Not yet...

same problem here, i tried install new update and now my phone don't turn on, only appears Qualcomm HS-USB 9008 when connecting usb

So apparently I never updated this thread... I ended up just RMAing my phone, but this is the bug that bricked my phone: https://bugs.archlinux.org/task/63370

Hardbricked when trying to install Linegae OS

Hi,
i think I hardbricked my Moto Z3 Play XT1929-8 when I tried to install Linegae OS 17.1 like described here https://forum.xda-developers.com/z3-play/development/lineage-os-moto-z3-play-t3873684 .
I successfully installed TWRP and tried to install the lineage zip from the thread with TWRP. The installation of Linegae locked successful for me. At the end of the Installation I got a message to reboot into the target System A or B where I selected B. This did not reboot instead there have been some mounting errors for 3 Partitions(I can't remember which one it was). After this TWRP asked me to reboot again. The result of this was the Hardbrick!!!
Now the device dosn't do anything when pushing the buttons. Especialy I don't get it into fastboot mode. When I connect via USB debian can't detect any device. dmesg repeats the following:
Code:
[952576.001408] usb 1-2: new high-speed USB device number 89 using xhci_hcd
[952576.129436] usb 1-2: device descriptor read/64, error -71
[952576.365420] usb 1-2: device descriptor read/64, error -71
[952576.601343] usb 1-2: new high-speed USB device number 90 using xhci_hcd
[952576.729392] usb 1-2: device descriptor read/64, error -71
[952576.965364] usb 1-2: device descriptor read/64, error -71
[952577.073403] usb usb1-port2: attempt power cycle
[952577.725243] usb 1-2: new high-speed USB device number 91 using xhci_hcd
[952577.725364] usb 1-2: Device not responding to setup address.
[952577.933337] usb 1-2: Device not responding to setup address.
[952578.141211] usb 1-2: device not accepting address 91, error -71
[952578.269197] usb 1-2: new high-speed USB device number 92 using xhci_hcd
[952578.269312] usb 1-2: Device not responding to setup address.
[952578.477351] usb 1-2: Device not responding to setup address.
[952578.685209] usb 1-2: device not accepting address 92, error -71
[952578.685294] usb usb1-port2: unable to enumerate USB device
Before I bricked my Device I got some version information via adb which might be helpful
Code:
[ro.build.version.all_codenames]: [REL]
[ro.build.version.ci]: [27]
[ro.build.version.codename]: [REL]
[ro.build.version.full]: [Blur_Version.28.11.27.beckham.retail.en.US]
[ro.build.version.incremental]: [5c49]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.qcom]: [LA.UM.6.2.r1-07200-sdm660.0]
[ro.build.version.release]: [8.1.0]
[ro.build.version.sdk]: [27]
[ro.build.version.security_patch]: [2018-04-01]
[ro.vendor.build.date]: [Sat May 5 08:17:33 CDT 2018]
[ro.vendor.build.date.utc]: [1525526253]
[ro.vendor.build.fingerprint]: [motorola/beckham/beckham:8.1.0/OPW28.70-25/5c49:user/release-keys]
[ro.vendor.build.thumbprint]: [8.1.0/OPW28.70-25/5c49:user/release-keys]
I can't understand why it hard bricked TWRP was successfully installed and if anything was wrong with the Linegae OS Installation it should boot into fastboot mode or TWRP? But the real big question is how to unbrick it? Am I right when I say the device is realy dead on any USB connection so I have to get deeper into the hardware to understand whats wrong? Could anyone help me doing this?
Best regards
Zeilentrafo

Got it to Qualcomm 9008 Mode
Ok so i played around a bit with volume down and power on and the USB problem in dmesg disappeared. Debian was now able to detect the Qualcom Chipset in 9008 Mode what is quite nice. I installed the qdl tool to flash it back to stock ROM. I although tried to talk with sahara to the Phone which worked. But I'm not sure where to get the right mbn file to flash the stock ROM? I googled around but I didn't find any site which was serious. From the unserious sites I've got a good locking firmware.
I'm not quite sure what is possible with the qdl tool and which files from the firmware have to be given? Can anyone explain this to me?
Best regards
Zeilentrafo

So you hard bricked your Beckham, and for what I read, you're using linux and now the phone is detected as Qualcomm 9008, right?
If you still unable to access the fastboot mode, I recommend you check https://forum.xda-developers.com/z3-play/how-to/how-to-restore-bricked-z3-play-t3986061.
It work for me on Ubuntu, tge Windows Qualcomm driver are really glitchy.
Once you are able to access the fastboot mode I recommend you flash this firmware first https://forum.xda-developers.com/z3-play/help/base-band-lost-brick-t3951484 (firmware in post 4).
That firmware helped me recover base band, Imei.
After that you should be good to flash whatever.
Also when usin TWRP to install Lineage, check to what slot the Lineage is being installed, normally is on the opposite slot (for A/B devices).
So when you hit the reboot on TWRP it will give you the options again to reboot system, reboot recovery or reboot slot A or slot B.
Select the one where it got flash and I then select reboot again.
You can make sure of where it got install on the aame flashing process details on TWRP