Related
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
donk232 said:
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Make sure you are using the oem usb cable. I had the same problem, changed cables and it worked
some cheap cables are for charging ... bt headsets and other stuff the data cables dont connect, its just for power.
koreancanuck said:
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
donks232 said:
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
Click to expand...
Click to collapse
You gotta make sure that your usb port is directly connected to your motherboard (usually back of your computer).
same usb port that has always worked. ive tried them all by now anyway
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
donks232 said:
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
Click to expand...
Click to collapse
lolol
Duno what happened but I'm glad it worked out for you
I'm having the same problem with my captivate after flashing REDROM. It won't recognize it if I have USB debugging turned on...
i have a theory... were you on a GB or other i9000 based rom/kernel???
well, im still having a problem getting my computer to recognize the phone, i have to mess with it for a a while to get it to work. i really want to flash anew 2.3.3 rom but without being able to get everything working right im stuck in 2.1
is this a problem with my cord or the connection on my phone? or something weird with my phone after flashing it a lot. its currently back to odin stock, i have been trying to master clear it with no luck
TRusselo said:
i have a theory... were you on a GB or other i9000 based rom/kernel???
Click to expand...
Click to collapse
continiuum miui and cyanogen mod are the only things ive tried to flash
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Guys, this problem while connecting to the PC body is stupidly charging .... Even in the download mode Odin does not see a body that could be? Connect other Cappy-all OK.
donks232 said:
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Click to expand...
Click to collapse
it must be a powered usb hub, on my buddies laptop only 1 out of 4 usb ports saw his phone.
if you can get into download mode you arent bricked.
try installing i9000 drivers, or try another computer.
I came up with this a while back. Could very well be the same issue.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Well since you can't use your phone you should sell it to me
Sent from my GT-I9000 using XDA Premium App
I didn't even install drivers, ubuntu got them for me
Sent from my SGH-I897 using XDA Premium App
psouza's one-click root is not working for me. when i try to run it, it says "searching for the phone" and hangs.
I just got a replacement from Verizon and i notice it is XT862. Does this matter?
I have the proper drivers installed, I have Debugging enabled, and it USB is set to Charge Only. Not using the original usb cable bc I don't have it (does this really make a difference??) but i have tried numerous different cables.
When I go into adb and type adb devices, it says list of devices is attached, and there are no entries. It seems my phone is not being recognized, despite the f
Any ideas???
Did you try mass storage or pc mode?
I had that issue with my USB cable. I used the one with my device and it didn't come up. I went grab another USB cable in the house and it worked.
yeah, tried them. Didn't mention that cause if I understand correctly, it should be in charge only.
thanks for the help!
I hope you figure something out good luck
Edit: have you tried running command prompt as administrator?
yeah. same result.
I read in another thread that you were required to us the cable that came with the phone for it to be detected. But also, I used a BlackBerry branded cable to do it on mine, and it worked.
come to think of it, i think i used a blackberry cable to root my first d3. will give it a shot and report back.
why the heck would it matter what cable you use? Though it doesn't make sense to me, it appears that the cable is indeed important.
SrulDog said:
psouza's one-click root is not working for me. when i try to run it, it says "searching for the phone" and hangs.
I just got a replacement from Verizon and i notice it is XT862. Does this matter?
I have the proper drivers installed, I have Debugging enabled, and it USB is set to Charge Only. Not using the original usb cable bc I don't have it (does this really make a difference??) but i have tried numerous different cables.
When I go into adb and type adb devices, it says list of devices is attached, and there are no entries. It seems my phone is not being recognized, despite the f
Any ideas???
Click to expand...
Click to collapse
Download the USB and Charging Drivers off of Motorolas website, make sure your phone connects to USB mass storage after you do this, then switch to charging mode.
It took a blackberry cable *and* reinstall of the moto drivers, but im up and running and rooted. now, to figure out how to get my other d3 to stop bootlooping...
glad to hear that you were able to root sorry about the bootloop though, have you tried using the SBF file to flash your rom back to stock to attempt again? i'm just getting into the d3 mod scene so i can't provide links to files or anything other than what i was told to do in response to questions i had and unfortunately that was one of them lol,
I had to use the cord that came with my phone. For some reason Motorola is bad about not using standards. For example there was an old 355 flip phone that is a Motorola I used to have and it wouldn't charge with anything but a Moto charger. It may be the same port but not the same compatibility. Thankfully it will accept a charge from any microUSB source.
Sent from my DROID3 using XDA App
Doesn't your phone have to have "USB Debugging" enabled as well?
USB Debugging enabled + choose Charge Only mode. That should do it.
LaZiODROID said:
Doesn't your phone have to have "USB Debugging" enabled as well?
USB Debugging enabled + choose Charge Only mode. That should do it.
Click to expand...
Click to collapse
yeah, to fiddle w/ any rooting, you need to have debug on
digitalsynner85 said:
glad to hear that you were able to root sorry about the bootloop though, have you tried using the SBF file to flash your rom back to stock to attempt again? i'm just getting into the d3 mod scene so i can't provide links to files or anything other than what i was told to do in response to questions i had and unfortunately that was one of them lol,
Click to expand...
Click to collapse
Yeah, I was able to flash the SBF. It was really exhausted and couldn't figure it out when I originally posted, but after a nights sleep, I was able to do it just fine.
Before I send my phone back to verizon, I was wondering - Is my phone still rooted after I flashed the SBF? I would ordinarily just run an app that checks, but i can't get past that annoying "activate your phone" screen.
SrulDog said:
Before I send my phone back to verizon, I was wondering - Is my phone still rooted after I flashed the SBF? I would ordinarily just run an app that checks, but i can't get past that annoying "activate your phone" screen.
Click to expand...
Click to collapse
that sucks that you're sending it back to verizon, hopefully next time when you root and rom, it won't botch the radio up lol
digitalsynner85 said:
that sucks that you're sending it back to verizon, hopefully next time when you root and rom, it won't botch the radio up lol
Click to expand...
Click to collapse
uhm, what are you talking about exactly?
my keyboard is broken so they sent me a replacement. It was during the process that I was trying to unroot the one thats going back to verizon that I softbricked it.
I have fixed it. Now I want to know if the phone is still rooted or not. And the radios have been totally fine the whole time.
SrulDog said:
uhm, what are you talking about exactly?
my keyboard is broken so they sent me a replacement. It was during the process that I was trying to unroot the one thats going back to verizon that I softbricked it.
I have fixed it. Now I want to know if the phone is still rooted or not. And the radios have been totally fine the whole time.
Click to expand...
Click to collapse
oh ok, you said you couldn't get past the phone activation screen, i thought you were saying that your radio got botched in the process somehow lol, my bad
SrulDog said:
Now I want to know if the phone is still rooted or not. .
Click to expand...
Click to collapse
if you used rsd to sbf you are no longer rooted.
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.
Has anyone run into problems with the Motorola Device Manager utility not recognizing the Moto X? I'm trying to RSD Lite back to stock so that I can install the OTAs but Moto Manager fails to update itself. I know that my computer can see the X as I was able to run ADB. However, every time I try to run Moto Manager I get a message that says "There are no updates for your device at this time. Current Version N/A"
I've tried uninstalling and reinstalling the device manager but it refuses to detect my phone. I've also toggled USB debugging on and off but it does not appear to be making a difference. My phone is a CDMA Dev Edition running mostly stock with a few Xposed modules.
Has anyone experience anything like this or know of any way to fix this issue?
-------Edited---------
I have resolved my issue. RSD Lite was useless and I was unable to get it working. I eventually used mfastboot to flash the stock img provided by Motorola. Everything works great now.
Island_King said:
Has anyone run into problems with the Motorola Device Manager utility not recognizing the Moto X? I'm trying to RSD Lite back to stock so that I can install the OTAs but Moto Manager fails to update itself. I know that my computer can see the X as I was able to run ADB. However, every time I try to run Moto Manager I get a message that says "There are no updates for your device at this time. Current Version N/A"
I've tried uninstalling and reinstalling the device manager but it refuses to detect my phone. I've also toggled USB debugging on and off but it does not appear to be making a difference. My phone is a CDMA Dev Edition running mostly stock with a few Xposed modules.
Has anyone experience anything like this or know of any way to fix this issue?
Click to expand...
Click to collapse
Are you on windows 8.1?
aooga said:
Are you on windows 8.1?
Click to expand...
Click to collapse
No, haven't updated to that yet. Still regular windows 8.
Island_King said:
No, haven't updated to that yet. Still regular windows 8.
Click to expand...
Click to collapse
Oh. then nevermind. There was another person on here who had a similar problem and it was fixed by going back to win8.
aooga said:
Oh. then nevermind. There was another person on here who had a similar problem and it was fixed by going back to win8.
Click to expand...
Click to collapse
Yeah, I saw that.
I was looking through the XDA guide on returning to stock, http://forum.xda-developers.com/showthread.php?t=2446515 and it looks like the reason why RSD Lite won't recognize the device is somehow related to the drivers that Moto Manager is responsible for. It seems like the other person didn't have the Moto Manager issue that I'm having (does not even recognize the device).
Does any one have any ideas or recommendations for what I should do to try and fix this problem?
I've attached a picture of the Motorola Device Manager update dialogue. As you can see, it says that the current version is N/A which I believe is causing the problem. The RSD Lite picture shows how the device is not being recognized despite being put into fastboot and connected to the laptop.
Island_King said:
I've attached a picture of the Motorola Device Manager update dialogue. As you can see, it says that the current version is N/A which I believe is causing the problem. The RSD Lite picture shows how the device is not being recognized despite being put into fastboot and connected to the laptop.
Click to expand...
Click to collapse
I didn't use Motorola device manager to rsd lite to stock, I just put my phone in fastboot Mode opened a cmd windo2 in adb, plugged my phone in using the USB cord and started rsd lite, you should see phone connected in the rsd lite window
Sent on my Moto X
flashallthetime said:
I didn't use Motorola device manager to rsd lite to stock, I just put my phone in fastboot Mode opened a cmd windo2 in adb, plugged my phone in using the USB cord and started rsd lite, you should see phone connected in the rsd lite window
Sent on my Moto X
Click to expand...
Click to collapse
I tried doing this. Still doesn't get recognized in RSD Lite. USB Debugging is enabled and RSD Lite is the newest version but I still can't figure this out. Is there any way to get the newest Moto X drivers without going through the Motorola Device Manager application?
And just to reiterate, my phone does show up on my computer so the USB cable is working.
Island_King said:
I tried doing this. Still doesn't get recognized in RSD Lite. USB Debugging is enabled and RSD Lite is the newest version but I still can't figure this out. Is there any way to get the newest Moto X drivers without going through the Motorola Device Manager application?
And just to reiterate, my phone does show up on my computer so the USB cable is working.
Click to expand...
Click to collapse
yes you can get the newest drivers without going through device manager. Don't know where but i see people post links to them so just search the internet. Another possible problem you might be having, is the phone connected via ptp or mtp. Moto device manager doesn't work when connected as ptp. Just pull down your notification bar and it will show you how it is connected. If it is ptp, change it to mtp. Then run moto device manager.
you guys on Win8/8.1, have you tried running Windows Virtual PC to trick MDM into working?
Hello,
I installed CM12 Stock ROM into the slot by mistake (yes kill me now PLEASE).
This supposedly changed the bootloader so I need to update jellybean bootloader to install something 2.x.
I had prepared the phone in Fastboot and before I downloaded bootloader the phone turned off, and now it won't do absolutely anything.
No combination of keys won't turn it on.Display does not come on after connecting to the USB / wall socket - not even the green light.
I tried a my friend's battery (fully charged) and also nothing.
Can I do anything at this moment except just throw it away ? (I am in CZ so visit Verizon is out of question).
I read there should be some special USB cable from Morotola and it allows flash without batteries (stupid?).
Thanks for the tips.
n31k said:
Hello,
I installed CM12 Stock ROM into the slot by mistake (yes kill me now PLEASE).
This supposedly changed the bootloader so I need to update jellybean bootloader to install something 2.x.
I had prepared the phone in Fastboot and before I downloaded bootloader the phone turned off, and now it won't do absolutely anything.
No combination of keys won't turn it on.Display does not come on after connecting to the USB / wall socket - not even the green light.
I tried a my friend's battery (fully charged) and also nothing.
Can I do anything at this moment except just throw it away ? (I am in CZ so visit Verizon is out of question).
I read there should be some special USB cable from Morotola and it allows flash without batteries (stupid?).
Thanks for the tips.
Click to expand...
Click to collapse
Cm12 does not change the bootloader, stock slot or not.
Cm12 installs fine on stock slot, if done correctly.
Sometimes when the Droid 4 is in AP fastboot mode it will power off after a few minutes of no activity.
Don't know what is causing the no boot option, if battery is charge.
the most common cause that hard bricks the Droid 4, is Flashing official firmware for a Razr xt912
Did you install Motorola Drivers?
Does Droid 4 show up in Device Manager?
See
Moto Drivers, RSD Lite, and other Unbricking Tools
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
Sent from my XT912 using Tapatalk
Thats the thing, the phone is not visible anywhere (Windows device manager, Linux lsusb).
I think that in this case none of the tools would help me (or it will ?)
n31k said:
Thats the thing, the phone is not visible anywhere (Windows device manager, Linux lsusb).
I think that in this case none of the tools would help me (or it will ?)
Click to expand...
Click to collapse
If Droid 4 will not connect to pc, you cannot flash firmware.
You can try a fastboot cable, but don't think that will help.
Motorola Fastboot/Factory Programming Cables Links
Sent from my XT912 using Tapatalk
Well I guess that changing the board is a way to go
If you press "Down", "Up" and "On" button - do you have menu?
Fervi
Hi please i need a help. I bricked my droid by Flashing official firmware for a Razr xt912 now the phone don't boot help please.
patsonator said:
Hi please i need a help. I bricked my droid by Flashing official firmware for a Razr xt912 now the phone don't boot help please.
Click to expand...
Click to collapse
Which bootloader version was on the phone?
Edit: Miss read thread title,
If you flashed droid razr firmware on your droid 4, there is no fixing
Sent from my Atom using XDA Labs