Database Develop

[Q] Phone won't connect to computer

Alright, so before I get flamed, I have searched for over an hour today, and I have not been able to figure this out. I am not new to android, rooting, custom roms, and editing files, so I have tried a multitude of different things.
To the point, my Droid 3 will not connect to my computer. It did a couple weeks ago when I flashed the Liberty Rom onto it, but now it'll just charge and not go into the USB mode. The only reason I know it is charging is when I disconnect the cord it says the disconnected message.
I have tried a couple different cables, and I usually use my stock cable that came with my D3. I have also tried restarting my phone and computer. I even flashed the newest Liberty Rom the hard way and still no luck.
If someone could please help me out I would be VERY grateful as this is a PITA!!!
Thanks in advance!

My two cents would be, try different usb port and make sure you have the most current moto drivers.
Have had luck with uninstalling driver pack and reinstalling.
Hope that helps.
Sent from my DROID3 using XDA App

I appreciate the help, unfortunately uninstalling the drivers didn't work, unless I didn't get the correct drivers? I went into uninstall programs. In the device manager nothing came up for my phone or drivers. And I have also tried different ports but to no luck. Thanks again for the reply.

Have you tried a different computer? A different device? Let's just rule out that this isn't a computer issue first...

My Zune works in all of my ports, and my other computer. My Phone however does not. It does the same thing as my other computer, although I guess I don't have the drivers on the other computer, but it would still come up as usb connection right? All this does is charge, sometimes.

Have you tried Linux? No drivers are needed. download a live CD and see if it helps.

eww245 said:
Have you tried Linux? No drivers are needed. download a live CD and see if it helps.
Click to expand...
Click to collapse
Can you explain?

("Very Important"!) PLEASE POST!!!
After sufferring through the same issue and delving deeply for almost two days,I have found the culprit!!! IT IS THE USB CORD AND NOT THE DRIVERS OR ANYTHING ELSE!!"SIMPLY USE THE FIRST USB CORD THAT YOU USED THE VERY FIRST TIME YOU PLUGED INTO YOUR COMPUTOR AND THAT WILL RECTIFY(FIX) YOUR PROBLEM.(IT HAS TO BE THE VERY FIRST USB CORD OTHERWISE YOU WILL CONTINUE TO HAVE THIS PROBLEM UNTIL AND NO OTHER COMPUTOR WILL RECOGNIZE YOUR DEVICE UNTIL YOU DO WHAT I SAY.I thought it was the rooting of my phone that initially caused the issue or maybe an app,however,I found the culprit.The usb cord!!!(WHATEVER USB YOU USED FOR THE VERY FIRST ,STOCK OR NOT,IT IS THE ONLY ONE YOUR COMPUTOR WILL RECOGNIZE!!! I HOPE THIS HELPS THE MANY OF YOU THAT ARE HAVING THIS SAME ISSUE AND GOOD LUCK
Sent From My Droid 3 using TapaTalk

xFreak-a-Zoidx said:
RECTIFY(FIX)
Click to expand...
Click to collapse
Thanks for clearing that up for me, I haven't competed the fourth grade.

Dude could've just said use the USB cord that came with the phone, to each his own. I have 6 micro usb cables and only the moto official will allow me to do anything other than charge the phone via cpu.
Sent from my DROID3 using XDA App

The only problem is that I ONLY use the cord that came with my D3... Any way to flash the stock rom onto my phone from my phone and unroot? Then I can take my phone into verizon and get a new one... and a new cord..

ajgates92 said:
The only problem is that I ONLY use the cord that came with my D3... Any way to flash the stock rom onto my phone from my phone and unroot? Then I can take my phone into verizon and get a new one... and a new cord..
Click to expand...
Click to collapse
That sucks. You can find the .890 sbf floating around in android development and flash it, I believe it takes everything to stock including unroot.
Sent from my DROID3 using XDA App

I looked in the thread posted, but the link to the flashable zip is down. So i'm stuck at a standstill right now.

This link works fine: http://dev-host.org/t6y98oinbk1f/Droid_3_SBF_5.6.890.zip

blmetzger said:
This link works fine: http://dev-host.org/t6y98oinbk1f/Droid_3_SBF_5.6.890.zip
Click to expand...
Click to collapse
Can I flash that wit cwm or the stock recovery though? I can't use RSD or fastboot because nothing happens when I plug my usb into it.

[Q] RSD Lite Won't Detect

Okay so I am having a little problem.
My phone when I boot it goes to a black screen after the safe system message becasue I didn't ever install a ROM on my safe system.
So I was going to go into RSD Lite to flash back or whatever, but my phone isn't detected.
- I have the newest Moto drivers, I've uninstalled fully and reinstalled
- I have the newest RSD Lite
- I have the original Bionic/Motorola Data Cable
- I can get into recovery/fastboot
- When I just plug my phone in while off, I see the little white LED
Any ideas?
My battery is about ~20% full, because when It was at 0% I couldn't get into recovery so I took it to a Verizon store and a lady there had a Bionic and she charged my battery for me. That's the only thing I can think of is that the battery has to be even higher like ~70% or fuller.
Thanks ahead of time
Note to Mods: Can I have my account verified because I was trying to just edit this thread and had to wait 5 minutes. I'm not a spammer lol

RSD Lite will only see my phone if I use the original cable that came with the phone.

BBQnBEER said:
RSD Lite will only see my phone if I use the original cable that came with the phone.
Click to expand...
Click to collapse
It has a M on the cable. It wasn't the one that came with my phone exactly but I got it from the Verizon store not a charging cable a Motorola Data cable. So IDK.

insane21m said:
It has a M on the cable. It wasn't the one that came with my phone exactly but I got it from the Verizon store not a charging cable a Motorola Data cable. So IDK.
Click to expand...
Click to collapse
Did you upgrade your windows OS recently? I've had a lot of driver issues since I've upgraded and haven't been able to figure out the solution other than reinstalling the drivers a few times. At one point I even needed to go into device manager to switch the adb driver to the moto fast boot driver.
Sent from my XT894 running CM10

danifunker said:
Did you upgrade your windows OS recently? I've had a lot of driver issues since I've upgraded and haven't been able to figure out the solution other than reinstalling the drivers a few times. At one point I even needed to go into device manager to switch the adb driver to the moto fast boot driver.
Sent from my XT894 running CM10
Click to expand...
Click to collapse
Nope but I've built a new computer that should be up and running tomorrow, will be dual booting W7 and W8 so I can try on both of those and get back to you.

Make sure you get the motorola usb driver package that has version 5.9.0. That needs to be installed as well as the other motorola drivers.
Good luck
Sent from my XT894 running CM10

danifunker said:
Make sure you get the motorola usb driver package that has version 5.9.0. That needs to be installed as well as the other motorola drivers.
Good luck
Sent from my XT894 running CM10
Click to expand...
Click to collapse
Thanks, do you have a link for that and the others? Just to make sure I'm installing the right things?

It still does not work..

Atrix HD bricked, RSD Lite recognizes the phone as Qinara, IMEI, Bootloader N / A

Ok, the phone - ATT Atrix HD - is bricked and turns on to a blank screen only. It seems to go to fastboot mode but RDS Lite 6.14 does not recognize the phone properly. The phone is recognized as Qinara S (not MB866) and the IMEI, bootloader, etc come as N / A like this:
IMEI/ESN/MEID: N / A
...
Bootloader Version: N/A
...
It is possible to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip following the instructions and everything seems to go fine but after the phone reboots everything stays the same as described above.
The phone goes to fastboot only by using power + volume down
I do not know how it got into that state - bought it like this, hoping to fix it
Any ideas?

grga1 said:
Ok, the phone - ATT Atrix HD - is bricked and turns on to a blank screen only. It seems to go to fastboot mode but RDS Lite 6.14 does not recognize the phone properly. The phone is recognized as Qinara S (not MB866) and the IMEI, bootloader, etc come as N / A like this:
IMEI/ESN/MEID: N / A
...
Bootloader Version: N/A
...
It is possible to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip following the instructions and everything seems to go fine but after the phone reboots everything stays the same as described above.
The phone goes to fastboot only by using power + volume down
I do not know how it got into that state - bought it like this, hoping to fix it
Any ideas?
Click to expand...
Click to collapse
Well if you got an awesome deal on it you can have it jtagged for 50
Sent from my Galaxy Nexus using Tapatalk 2

Not that awesome as I noticed a small crack on the screen (maybe the screen does not work at all). Well, I knew what I was getting in. Still, good to know that jtag is an option, thanks.
Btw, probably the way it shows in RSD Lite is not a problem. The driver seems to be the correct one and it responds to fastboot commands properly. I also attached a working Atrix HD, and it also shows the same way. The bootlooping is the concern. When connected to computer without enabling fastboot mode it first shows as Motorola USB Networking driver in device manager, then in Human interface devices then the same repeats. I am using factory-like cable. Out of curiosity, has anybody experienced this?

grga1 said:
Ok, the phone - ATT Atrix HD - is bricked and turns on to a blank screen only. It seems to go to fastboot mode but RDS Lite 6.14 does not recognize the phone properly. The phone is recognized as Qinara S (not MB866) and the IMEI, bootloader, etc come as N / A like this:
IMEI/ESN/MEID: N / A
...
Bootloader Version: N/A
...
It is possible to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip following the instructions and everything seems to go fine but after the phone reboots everything stays the same as described above.
The phone goes to fastboot only by using power + volume down
I do not know how it got into that state - bought it like this, hoping to fix it
Any ideas?
Click to expand...
Click to collapse
Did you check this?
http://forum.xda-developers.com/showthread.php?t=2057078
do not forget to eraser step operation=”getvar” var=”max-download-size”
here you find the SBF file.... do not forget the FW
http://sbf.droid-developers.org/dinara/list.php

Yes, I did that with MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip. After deleting the lines from the xml it went without errors but didn't change anything. Btw, what do you mean by "do not forget the FW"?
The driver for fastboot is Mot Single ADB Interface ver 1.2.14.0. Is that what it should be?

grga1 said:
Yes, I did that with MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip. After deleting the lines from the xml it went without errors but didn't change anything. Btw, what do you mean by "do not forget the FW"?
The driver for fastboot is Mot Single ADB Interface ver 1.2.14.0. Is that what it should be?
Click to expand...
Click to collapse
Yes.
the firmware(FFW)....I test today and I use the firmware 20 .....

Ok, thanks, so I guess as SirHoover says probably the only option is jtag.
Does anybody know if the bootloader gets flashed with RSD Lite / fastboot? Is it possible to flash it at all on these devices? I think it is possible on the google phones.

Just to close the topic. I opened the phone and there seems to be a physical damage to the phone - the main board is slightly bent, so I guess that is the reason for the strange behavior. At least I can stop digging into that .
Thanks to all that tried to help.

Hello guys! Need some help please..do anybody have a genuine firmware back up for ahd jelly bean? I'm using one flashable thru rsd,but its given me problems,many bugs.I'm not even rooted.I'm thinking a genuine 4.1 file system would do fine..any ideas?
Sent from my MB886 using xda app-developers app

grga1 said:
Just to close the topic. I opened the phone and there seems to be a physical damage to the phone - the main board is slightly bent, so I guess that is the reason for the strange behavior. At least I can stop digging into that .
Thanks to all that tried to help.
Click to expand...
Click to collapse
I feel your pain I bought a gnex and opened t up yesterday to find it had water damage and damage to the board. This explains why stuff is going wrong.

I have the same problem. RSD does not see the phone and it shows up in device manager as Fastboot Qinara S but with a yellow exclamation mark, How do I make RSD Lite connect with the phone. Am i missing a driver somewhere

Moto X won't turn on

I was rooting my phone I got to the point where I accepted the 4.4 update it downloaded installed shut off and that was it. I have tried every button combination, It had plenty of charge, and just to make sure I plugged it into a wall charger for 20 minutes. Any suggestions? The screen doesn't come on at all. Thanks, Garrett.

Follow the instructions on how to enter stock recovery. This should help.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/94946/p/30,6720,8696
Sent from my XT1060 using Tapatalk

Still no luck...

garrettpen said:
Still no luck...
Click to expand...
Click to collapse
Sorry bud. Sounds like you might have bigger issues than I can help you with. However, you should try to connect it to your computer and see if you get anything. Also keep trying to power it on while on a USB or charger.
Hopefully someone with a similar experience can chime in.
Sent from my XT1060 using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2477132
You can try to flash your phones stock ROM using this tool kit if you can get into the Boot loader. I just used it to flash back to stock on my sprint moto x. I know you are in a different situation but I can't hurt to try
Sent from my XT1056 using Tapatalk

garrettpen said:
I was rooting my phone I got to the point where I accepted the 4.4 update it downloaded installed shut off and that was it. I have tried every button combination, It had plenty of charge, and just to make sure I plugged it into a wall charger for 20 minutes. Any suggestions? The screen doesn't come on at all. Thanks, Garrett.
Click to expand...
Click to collapse
hold power button for 1 min if you feel the phone vibrate that is good.
now try holding Volume Up + Power will it boot into the bootloader.
If yes great time to restore to stock
If No then your phone is hard bricked and you will have to get it replaced.
one easy way to find out if your phone is hard bricked is to plug it into the computer and see what drivers it tries to install
if it say qhsusb_dload then i know for a fact that your phone is Hard bricked.
If that is the case call your carrier or go to a local store and tell them that your phone was on 4.2.2 and you downloaded the 4.4 OTA and it rebooted to install it and now it won't turn on at all they should give you a brand new phone because it was the phones problem.
When you get your new phone please post here first with What Carrier Moto X you have and what android version it is on 4.2.2 / 4.2.2 Camera Update / 4.4. and i will help you get your phone rooted and up and running correctly
Good Luck My Friend and please don't be afraid to ask for help

Mist likely hard bricked, you're not the only person this has happen too and won't be the last, if you're getting the driver mussing as previously posted ,I agree and its hard bricked. Which 4.2 stick firmware where you on? Pre camera update? At least you can call you're carrier and say you attempted to install an ota which in fact did brick your phone don't tell them you tried to root it of course, good.luck
Sent on my Moto X

Bricked device and totally lost :(

I'm having a lot of trouble with a device and I'd like to share with you guys and try to come to a solution for it.
I have a XT1068 that got its battery depleted during the flash of a stock rom, with the stock bootloader and everything. I've been looking for information and it really looks like a bootloader brick, or so I've been thinking of it and by that the phone doesn't give not even a sign of life. The only thing that if gives is that plugging it into USB charger the led turns on for two minutes or less. When connected to the computer, device is only recognized after led turns off and being read first as QHSUSB_BULK and Qualcomm right after it.
Looking for tutorials on the Web I've found motoflasher and blankflash,
I've found out that motoflasher does the same as blankflash, but in a more intuitive way, I've found out a solution for XT1032, but I think that it works for XT1068. Problem is I think that it can't be done after the bootloader was already updated for 5.x, I can't find a qboot.exe that is compatible with 5.x bootloader. If someone also got stuck and got rid of it please help me, I'm desperate for a solution of it.
I've also got a XT1038 that works perfectly with 5.1, I'd like to know if there is a way of backing up my bootloader for use in this another device.
Thanks for everything and sorry for my English, I'm Brazilian and Portuguese is my main language.

wrong forum this is moto g 2014 2nd gen XT1063/4/8/9
try link below
http://forum.xda-developers.com/moto-g

I'm sorry, my autocorrect changed the device name. It is indeed a XT1068.

foooxxx369 said:
I'm sorry, my autocorrect changed the device name. It is indeed a XT1068.
Click to expand...
Click to collapse
dont think there is a fix for xt1068 ,
theres a fix for xt1032 I believe if still on kitkat boot loader
sure i seen reports that if this happens to xt1068 theres no fix except service center who replace motherboard - but please check my info is from months ago

I have a similar situation with my XT1063. I can enter on bootloader and recovery and even boot normally to system but I get Forcé Close to EVERITHING so the phone is useless. And when I try to flash another ROM vía recovery or adb or fastboot there are a error por fail. So I am not able to change my recovery, restore a backup , flash new ROM (even the stock one 5.0.2) or anything. I read also all the thing about OP's driver solución (qboot) but my pc recognice my phone by xt1063...
Sent from my Optimus 4X HD using XDA Free mobile app

i'm on the same boat. Hopping on it

the qboot thing is gen 1 on kitkat bootloader - so wont work on gen 2
the cant flash recovery / rom thing is corrupted emmc (either file system or just bad)
both still no further advance -sorry guys........