Related
recently in the last few days ive been having problems with my phone .
when plugging in the usb lead from pc to transfer files ,the computer doesnt detect the phone correctly and i get a usb error . tried hard reset etc no difference .
wifes phone connects perfectly . using darkys 7.6 rom on both phones
when i remove the usb cable the phone still indicates that its charging and will continue to do so until i remove battery and restart phone .
the phone detects the cable as it does the indicator bleep ,but i get no mass storage notification.
just hoping the usb connector isnt damaged internally ,doesnt feel loose and the phone is looked after also its the 16 gb version which arent available anymore.
I've a problem after (more than one) firmware update....
My P970 don't recognize recognize charger & don't go in USB mode (PC don't view the SD card)
I try CM7 and Nova, I also have a brick after flashed a kernel Nova in a Rom stock.
After that I put a new Rom stock v10c by KDZ but now have this terrible problem....
How can I solve it....?
Many thanks
have you tried to do an hard reset?
interdan said:
have you tried to do an hard reset?
Click to expand...
Click to collapse
Yes by enter in the hidden menu (3845#*970#) but nothing change....
I have the same problem since 2 months. I'm currently with the last temasek Kang release, kernel nova 11c.
The only way to charge correctly the battery is to wait the phone self extinction, by low battery, wait around 10 minutes, and plug the charger. Another weird thing: when I plug the shut down phone to sector, it will autoboot (everytime).
Else, when I try to charge the phone, 2 different behaviours:
1) most of time it charges anyway, but not detected as charging. The phone overheat, and could self extinct because of that. Time of use with a battery charged like that is very poor.
2) sometimes, nothing happen. No charge.
I'm very bored by this bug.
Sent from my LG-P970 using XDA App
gornog said:
I have the same problem since 2 months. I'm currently with the last temasek Kang release, kernel nova 11c.
The only way to charge correctly the battery is to wait the phone self extinction, by low battery, wait around 10 minutes, and plug the charger. Another weird thing: when I plug the shut down phone to sector, it will autoboot (everytime).
Else, when I try to charge the phone, 2 different behaviours:
1) most of time it charges anyway, but not detected as charging. The phone overheat, and could self extinct because of that. Time of use with a battery charged like that is very poor.
2) sometimes, nothing happen. No charge.
I'm very bored by this bug.
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
Check your USB cables, the pins inside. As well as the USB connector on the phone itself. Use a different cable. I/we never had this kind of problem (not charging so it isn't a bug or something but rather hardware problem. If not USB, battery problem.
If not, do a full wipe and reflash the KANGed RC0. If problems persists, revert to Froyo stock so you could test. I'm after the warranty for you if you still have the problem in Froyo.
That auto reboot is well known for CM7. Again, this also is not a bug but a feature.
gabwerkz said:
Check your USB cables, the pins inside. As well as the USB connector on the phone itself. Use a different cable.
Click to expand...
Click to collapse
Checked with 3 different cables and several chargers (including original ones). Phone USB connector seems OK, but cannot really check it.
gabwerkz said:
battery problem.
Click to expand...
Click to collapse
2 batteries. Reproducible.
gabwerkz said:
If not, do a full wipe and reflash the KANGed RC0. If problems persists, revert to Froyo stock so you could test.
Click to expand...
Click to collapse
Did full wipes several times, but no effect. It's hard to go back to stock Froyo without phone-to-computer connection, and I don't want to loose ability to root my OB after that.
gabwerkz said:
That auto reboot [...] is not a bug but a feature.
Click to expand...
Click to collapse
OK
Anyway, thanks for all. If we are only few people with this bug, it seems to be a material failure indeed.
I may look for the warranty, but as I changed country (from EU to Canada), it will be quite complicated, and I need my phone :/. Just a (stupid) idea, maybe the phone didn't support the 110V, after 220V charging usage (but charger should support these 2 voltages).
If not, do a full wipe and reflash the KANGed RC0. If problems persists, revert to Froyo stock so you could test. I'm after the warranty for you if you still have the problem in Froyo.
Click to expand...
Click to collapse
I come back to v10b europe, across a lot of wipe....
Fortunatly the charger was recognized....
The problem was't "don't charge" but "not recognized"
Unfortunately today try to flash the Quasar kernel, and now I have the same problem.....
The charger, charge, but don't recognized and the USB to PC don't work's.....!!!
Turn phone off
Remove battery
Wait 10 seconds
Put battery back.
Turn phone on
I had this issue on my Optimus Black with stock Froyo rom.
My symptoms were:
- device recognized as 'modem' in Windows but no option in Android to switch into "USB Mode". Phone update software would still recognise phone was connected and I could run a firmware recovery using LG tools. Reflashed and reset to factory many times didn't fix the issue.
- if phone switched off and plugged into charger or USB would go into "SW Upgrade" mode
- I could force "USB mode" to appear on the phone by opening the hidden menu and switching the USB to "AP Mode" I think it was.
- I found the USB connections would disconnect after a period of time and sometimes the "AP mode" workaround wouldn't work.
- tried different cables, chargers and PCs and all present the same problems.
- having the battery unplugged for an extended period would get the phone working temporarily but the problem would come back after a short while.
Eventually got on to LG Support and sent it off for repair. They replaced the motherboard as faulty.
I think the problem may have been caused by a faulty car charger that I have since replaced, but ultimately replacing the motherboard on the phone fixed the problem.
If your phone is covered under warranty, I'd be sending it off for repair as it is probably a hardware issue.
brownowski said:
I had this issue on my Optimus Black with stock Froyo rom.
My symptoms were:
- device recognized as 'modem' in Windows but no option in Android to switch into "USB Mode". Phone update software would still recognise phone was connected and I could run a firmware recovery using LG tools. Reflashed and reset to factory many times didn't fix the issue.
- if phone switched off and plugged into charger or USB would go into "SW Upgrade" mode
- I could force "USB mode" to appear on the phone by opening the hidden menu and switching the USB to "AP Mode" I think it was.
- I found the USB connections would disconnect after a period of time and sometimes the "AP mode" workaround wouldn't work.
- tried different cables, chargers and PCs and all present the same problems.
- having the battery unplugged for an extended period would get the phone working temporarily but the problem would come back after a short while.
Eventually got on to LG Support and sent it off for repair. They replaced the motherboard as faulty.
I think the problem may have been caused by a faulty car charger that I have since replaced, but ultimately replacing the motherboard on the phone fixed the problem.
If your phone is covered under warranty, I'd be sending it off for repair as it is probably a hardware issue.
Click to expand...
Click to collapse
All of my thanks.....
I've the same problems.... All as you described!!!!
So after Christmas time, I'll go to an LG support!
problem found
I own a celular repair shop in baja california mex. and resently some one brougth a LG Optimus Black p970 with same simptoms ,heat,no power no usb conectiviti and chargin problems I found a conector on the inside part of the device with some visual damage (over heat) plastic melted just a minimun part of it so i check the hole conector and I found that two conections were lost by the overheat problem
this is coused by the charging conection bad design
Ask no Problem
I'm having same problem as stated by others. This is annoying me.
Its just been 2 months I've got this phone and it feels real bad to face such problems so soon.
Am facing problems like. I connected my phone to PC via USB and it showed me the option to Turn on Mass Storage, I clicked on it and it showed me the Mass Storage Drive on my PC too. But in just minute or two it disconnected on its own and SD Card started scanning and again it got connected by its own but then after that it disconnected again and it on pc it started to install drivers again. Which were already installed like 5 or 6 of them.
I formatted the phone twice. Removed the battery for around 5-6 minutes. Used like 4 USB cables. Installed LGE drivers from LGE Software updater.
This is so bad.
What software are you guys using? Which ROM?
I've also been experiencing this situation, one time this problem caused a loss of all my SD data! (my sd card got corrupted)
I'm on Zeus V6.11 right now, and I must say that USB storage is working great for me in CWM Recovery, even though it doesn't work on my phone when it's turned on in Android.
How to check whether it's an hardware problem in my phone, or just a fault of my compuer?
Experiencing this problem for around two months now. I suspect my charger to be damaged. Since I can charge the phone via the USB port. When I try to charge the phone via the charger it doesn't respond, but when I pull it off the charger the phone will boot. Had the motherboard already replaced by LG service center, but the problem wasn't solved.
The phone can connect to PC without any problems. PC can connect to mass storage.
So now, I'm using a Corby II charger and it seems to do a great job at charging my OB
N00BY0815 said:
What software are you guys using? Which ROM?
Click to expand...
Click to collapse
Currently I'm using Stock Root v20b rom.
No software's nothing, as I stated I even formatted my phone twice.
It was working well around 2 days back. I had just plugged my usb cable to phone via pc and then all of a sudden the phone started acting weird, like it was connecting and disconnecting frequently, and then it started to install the LGE drivers by itself, which were already installed didn't even touch them nor uninstalled anything.
Tried using Sony Xperia Neo V's USB cable too, but no luck.
Once I lost my USB cable.
then i brought a cheap uUSB cable. Icud transfer data from PC, but charging rate was really very SLOW... nearly 4hr.!!
Now i replaced it with new Original one, n every thing working Perfect...
I am seeing the same problems - charger is not recognized and USB mode is not working. Different cables / chargers, different Win7 and Ubuntu PCs.
I formerly used a rooted V20o from here, with which the problem first appeared, now I went over to Zeus 6.22, which still shows the same problems.
I believe the hardware is faulty.
Can anybody help me how to regain warranty? I have the stock V20o (unrooted), but since USB does not work, I cannot flash it the regular way. Is it possible now to flash from sd card?
Try with LG standard update software, you have the emergency menu....
If you want to viwe your sd card try the Samba Filesharing app. I have the same problem on cm7 and with this App i can see my SD Card
Ok guys, I bought a Droid 4 with a "battery problem" the battery flex cable was ripped so I tought just a new battery and the phone would be ready to go, without battery I connected the phone to the usb port of my PC and a green led appears, that was good news, a sign of life of the phone.
I received the battery today, i connected it and the problem was worse, I have no video, no sound, neither the led light, the digitizer keys and the keyboard doesnt turn on, I tought the battery came DOA, but when I connected the phone to the PC was recognized by the PC because the Motocast partition appeared, the somehow i just managed to boot on fastboot, and is working too... but, then, what exactly is the problem?
I dont have:
No Lights (led, keyboard, digitizer)
No Screen
No Sound
No vibration
No touch feedback
I have:
Power
Can enter Fastboot
Maybe its bricked and just flashing ICS would resolve the problem?? I have no warranty, so i don't have nothing to lose (only money from the phone and the battery lol), the phone doesn't have water damage, its in excellent condition, the phone doesn't have signal to be opened before, but still is a probability because the battery was originally rippered... and maybe that is a signal that the previous owner was someone like us and the flashed GB when he was on ICS and maybe the bricked the phone? I don't know... I'm going to flash the fastboot ICS to see if maybe can come to life, but i need to work now... maybe later.
UPDATE:
OK, ITS BRICKED, I dont know how, but Its bricked, since i can't see nothing i booted in fastboot and then tried to flash the stock .217 ICS firmware with RSD Lite, but i'm getting errors... and I have low-battery, and tried to flash using The Project's Eternity EPRJ_Fla****RZR_Windows, but still with the low-battery issue, i removed the battery and plugged to a universal charger to gain some charge and try later... maybe I can rescue this phone.
Have you tried using a fastboot cable? If the battery is low and you are using a normal cable, it won't (sometimes) charge and definitely won't let you flash anything in fastboot.
VZW recently sent me a replacement D4 with a very low battery, and when I plugged it in it would not charge (!). Hooked it up with a fastboot cable and it started right now, charged it, and good to go.
The problem is not the battery, I thinked about getting a fastboot cable, but instead of spending $10, y just unplugged the battery and putted on a universal charger, it worked, i entered to fastboot mode, i flashed .217 firmware, and also used the Droid 4 ICS Utility to flash .217 firmware again and WIPE all data. But again i tell that I have NO DISPLAY, NO VIBRATION and NO LIGHTS, the led lights works sometimes, but no display, vibration and keyboard lights is weird, i connect the phone to the PC and can access to MOTOCAST... but why??? maybe I need a HDMI cable to see outside the display, maybe the LCD and digitizer are broken, but no, they are on excellent condition and the ribbon cable between the two bodies are intact... nothing is loose inside.
I have a T-Mobile Note 4 with RAPTURE ROM installed, and about a month ago I noticed that it wasn't charging very fast ("USB" charging speed even when plugged in with original charger and cable). When plugged into a PC, even in ODIN mode, all I get is "USB Device Not Recognized".
I had a phone repair shop replace the charging port, thinking that was the problem, yet it still persists. I really have no ability to test if it's a ROM issue, because to go back to full stock requires that ODIN recognizes the phone...
Any suggestions? I have searched high and low and can't find a resolution. I even tried restoring to an earlier TWRP backup with a different ROM and also got the same result.
the easy way to test if it is a rom issue or usb issue, boot your phone odin mode, and connect to computer, if computer recognized your phone, then better change your rom, if same issue then your phone may have hardware issue.
most repair shop check only usb charging after they fix it. they dont check computer connectivity.
based on my experience, your phone charging port is not working, some pins aren't touching the board. but the positive and negative pin for charging are OK.
You should take it back to the shop to double check it again.
I have a stock Droid 4 with a mugen power extended battery. Last night I got a vibration that felt like a Facebook notification on my Droid 4. I pulled it out of my pocket and tried to turn it on, but the screen remained black. I tried holding the power button to reset it, but there was no response. I tried plugging it into my wall charger that usually works with a usb cable that also usually works, but even after an hour, there were no signs of life. I tried plugging in the cable to my tablet, and it charges just fine. I've used other cables and chargers, still no luck.
I tried plugging in into my laptop with the cable I normally use for charging and my laptop picked up that a device was connected. I looked in My computer to see if I could access the phone internals, but I just saw a drive letter with motocast, and 2 other drive letters that told me to insert disks in to them. The motocast drive letter had what looked like motocast system files, but that was it. I had an SD card in my phone, but no drive letters that came up when I plugged the phone it let me access it. When I went to safely remove it, I saw in the device manager that it correctly identified that a Motorola XT894 had connected to it, and I safely removed. I've tried doing a soft reset, holding the power down+vol down button for 10 secs, but that does nothing. There are no lights at all, not even when I plug/unplug it from the charger.
I'm planning on going to a cell phone repair place today to have them remove and troubleshoot the battery ( I don't have plastic torx and I'm afraid of short circuiting the motherboard)
I feel that there is some hope for fixing the problem or at least data recovery since windows recognized my phone and I could at least get to the motocast folder on it. I do wonder why my phone is able to be recognized by my computer but still show no signs of life otherwise. Any ideas?
I love this phone, but it sucks with this happening around the holiday season.If it can't be fixed, I'd at least like to get my data off it. Please help!!
Is there any way to fix this? Would physically removing and reinstalling the battery work? Do I have any options for file recovery off my phones internal storage, especially since it seems windows recgnizes that my phone is connected?
UPDATE: Got it to power on and boot normally once. Enabled USB debugging when I had the chance.
Got back from the cell phone repair place this morning. He said the battery was definitely bad, drawing zero amps. He also said he was getting weird voltage spikes throughout the board, and I think he said something about the PCMI power management chip being bad and that the phone was done for. I told him that I could plug the phone into the the computer and it recognized it. He said my best bet might be getting a battery off eBay that would power my phone long enough to get everything off of there. I asked if it could also be USB cord related as I tend to have horrible luck with them. He said it could be and that the reason that I was able to have the phone recognized by USB but not charge is due to different pins communicating during USB connection. I'm including these details so you can gauge this guy's expertise. He did go from saying the phone was done to suggesting a new battery/USB cord, and I was able to power it on after using said cord.
I went and bought a new USB cord and plugged it into my inverter I had in my car. To my surprise after a few seconds, the phone was showing the charge screen with the battery at 70%. It still wouldn't boot up so I kept it plugged in for about 5-10 mins. Eventually it did boot up. I immediately went in and enabled usb debugging. All my data was there. For a brief bit the date and time was off, but even that corrected itself. I played a song from my music collection on my SD card to make sure that was OK. The song played, and shortly thereafter it looks like the phone powered back off as it had originally done. I hooked it up to my computer and my PC started installing new hardware, it said something about xt894(my phone) a couple of disk drives and a CD ROM drive, and something about adb. The furthest they got were as unknown devices, so I disconnected them and reconnected them a couple of times, eventually the install icon went away. It still recognizes the phone and even recognizes there is a storage device with the phone in the device manager menu, but it still says "please insert a disc into drive (letter)" The drive with just motocast is still there, and I think there was another CD ROM that was recognized, said to insert a disc same as the drives. I threw it on my wall charger for a few minutes, but it still wasn't powering on. I then realized that charging it could exacerbate the voltage spikes the guy was talking about, and I didn't want to risk it especially after seeing all my data there, so I unplugged it.
I do have the battery that the extended battery replaced. It had to be pretty much tied to a charger, but it did work if only for less than half an hour. So there is the option of using that to temporarily power the phone.
My new questions are:
Am I at risk of further board damage if I charge/power on the phone? What about charging the degraded but functioning battery?
Now that I know I have USB debugging enabled and my computer still recognizes my phone, how do I go about backing up the contents of my internal storage?
Could this all be effectively solved by just getting a new battery? What about what he was saying with the weird voltage spikes and PCMI chip?
RyanV-M said:
UPDATE: Got it to power on and boot normally once. Enabled USB debugging when I had the chance.
Got back from the cell phone repair place this morning. He said the battery was definitely bad, drawing zero amps. He also said he was getting weird voltage spikes throughout the board, and I think he said something about the PCMI power management chip being bad and that the phone was done for. I told him that I could plug the phone into the the computer and it recognized it. He said my best bet might be getting a battery off eBay that would power my phone long enough to get everything off of there. I asked if it could also be USB cord related as I tend to have horrible luck with them. He said it could be and that the reason that I was able to have the phone recognized by USB but not charge is due to different pins communicating during USB connection. I'm including these details so you can gauge this guy's expertise. He did go from saying the phone was done to suggesting a new battery/USB cord, and I was able to power it on after using said cord.
I went and bought a new USB cord and plugged it into my inverter I had in my car. To my surprise after a few seconds, the phone was showing the charge screen with the battery at 70%. It still wouldn't boot up so I kept it plugged in for about 5-10 mins. Eventually it did boot up. I immediately went in and enabled usb debugging. All my data was there. For a brief bit the date and time was off, but even that corrected itself. I played a song from my music collection on my SD card to make sure that was OK. The song played, and shortly thereafter it looks like the phone powered back off as it had originally done. I hooked it up to my computer and my PC started installing new hardware, it said something about xt894(my phone) a couple of disk drives and a CD ROM drive, and something about adb. The furthest they got were as unknown devices, so I disconnected them and reconnected them a couple of times, eventually the install icon went away. It still recognizes the phone and even recognizes there is a storage device with the phone in the device manager menu, but it still says "please insert a disc into drive (letter)" The drive with just motocast is still there, and I think there was another CD ROM that was recognized, said to insert a disc same as the drives. I threw it on my wall charger for a few minutes, but it still wasn't powering on. I then realized that charging it could exacerbate the voltage spikes the guy was talking about, and I didn't want to risk it especially after seeing all my data there, so I unplugged it.
I do have the battery that the extended battery replaced. It had to be pretty much tied to a charger, but it did work if only for less than half an hour. So there is the option of using that to temporarily power the phone.
My new questions are:
Am I at risk of further board damage if I charge/power on the phone? What about charging the degraded but functioning battery?
Now that I know I have USB debugging enabled and my computer still recognizes my phone, how do I go about backing up the contents of my internal storage?
Could this all be effectively solved by just getting a new battery? What about what he was saying with the weird voltage spikes and PCMI chip?
Click to expand...
Click to collapse
Have you tried it without the extended battery. That could be the culprit of all this going on. If your original battery is bad get a new one and charge it. I had the same problem with a battery till I bought a new oem battery. After I charged my Battery I had to go to fastboot to get device to boot with a fastboot cable. Then while connected to that cable I backed up my contacts. Then while still connected to fastboot cable I flashed stock firmware and started all over again havnt had a problem since.
I'm waiting on an OEM battery to arrive. I was able to save everything off my SD card that was in the phone, so I am increasingly hopeful. Do you have to go into fastboot if your phone is stock? What is fastboot even?
RyanV-M said:
I'm waiting on an OEM battery to arrive. I was able to save everything off my SD card that was in the phone, so I am increasingly hopeful. Do you have to go into fastboot if your phone is stock? What is fastboot even?
Click to expand...
Click to collapse
AP fastboot mode is where where you flash stock while connected to rsd lite via usb or fastboot cable. It is part of bootloader. You hold down all three buttons to get to boot menu scroll down to ap fastboot then hit the vol. up button then connect to computer after you have rsd lite active. then flash stock firmware. If you get a battery that doesn't charge have them send you an other one that has happened to me a few times but not many. Remember when you scroll in boot menu you only have a few seconds to pic what you want to do or the device will try to boot.
The OEM battery I ordered finally came yesterday (no thanks to USPS). I tried multiple chargers and outlets with a good cable, and still nothing. I have another non-OEM battery arriving tomorrow, hopefully this one was just a D.O.A battery.
RyanV-M said:
The OEM battery I ordered finally came yesterday (no thanks to USPS). I tried multiple chargers and outlets with a good cable, and still nothing. I have another non-OEM battery arriving tomorrow, hopefully this one was just a D.O.A battery.
Click to expand...
Click to collapse
It was probully a dead battery. It sat for to long. If you had a fastboot cable cable you wouldn't need a battery to flash it in rsd lite or just to see if it would boot. There was this one time I had to order 3 battery's just to get one that worked. Sometimes they been sitting for to long being the device was made in 2012.
OGdroidster said:
It was probully a dead battery. It sat for to long. If you had a fastboot cable cable you wouldn't need a battery to flash it in rsd lite or just to see if it would boot. There was this one time I had to order 3 battery's just to get one that worked. Sometimes they been sitting for to long being the device was made in 2012.
Click to expand...
Click to collapse
So your saying if I had a FastBoot cable I could boot my phone without a battery in the phone? Would it wipe my internal data/OD?
Update: I have had a BIN-TEK battery charging for several hours, still nothing. Good cord and charger too. The only other options I have is the extended battery that crapped out on me but powered on briefly, or the puffed out factory battery it replaced. Things are looking bleak
OK
RyanV-M said:
So your saying if I had a FastBoot cable I could boot my phone without a battery in the phone? Would it wipe my internal data/OD?
Update: I have had a BIN-TEK battery charging for several hours, still nothing. Good cord and charger too. The only other options I have is the extended battery that crapped out on me but powered on briefly, or the puffed out factory battery it replaced. Things are looking bleak
Click to expand...
Click to collapse
It is so you you can get to fastboot mode so you can flash. It is usable with a low battery or no battery at all. When you first connect it to computer it will automatically start booting. Here is a link for one: https://www.amazon.com/gp/aw/d/B00K...boot+cable&dpPl=1&dpID=41ep3FoxgHL&ref=plSrch
If it boots to your ROM when you first connect it then you have battery problem. If it does not boot to rom then you should leave it connected and flash stock firmware from fastboot mode witch you will need rsd lite to flash. If it boots after that then it us just a battery problem. If nothing happens then you probully need a new droid 4. Remember once you disconnect fastboot cable device will go off. So don't disconnect until you are done with everything being that you don't have a good battery.
I have a fastboot cable now. Haven't tried anything yet but I plan to today. I've looked around XDA for firmware If I need to flash stock firmware, I found several versions for the Droid 4 here:https://forum.xda-developers.com/droid-4/general/droid-4-xt894-firmware-mirrors-2015-t3004048 how do I know which firmware is correct?
Also, am I good to disconnect the fastboot cable from the PC as long as I am NOT in the process of flashing firmware?
I have ADB debugging enabled on my phone, and last I checked my computer recognized my phone, just couldn't access internal files on my phone. (Had "Please insert disk into drive x" message) Any options there?
RyanV-M said:
I have a fastboot cable now. Haven't tried anything yet but I plan to today. I've looked around XDA for firmware If I need to flash stock firmware, I found several versions for the Droid 4 here:https://forum.xda-developers.com/droid-4/general/droid-4-xt894-firmware-mirrors-2015-t3004048 how do I know which firmware is correct?
Also, am I good to disconnect the fastboot cable from the PC as long as I am NOT in the process of flashing firmware?
I have ADB debugging enabled on my phone, and last I checked my computer recognized my phone, just couldn't access internal files on my phone. (Had "Please insert disk into drive x" message) Any options there?
Click to expand...
Click to collapse
You have the right index get the one says
4.1.2 - VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip just in case you need to flash. just connect cable and see if device boots if not flash the firmware with rsd lite. never umplug cable unless you want the device off because when cable is is pulled the device will go off.
I connected the fastboot cable without a battery in the phone. Held power button, computer detected it. Said it had found an XT894 and Motorola Network drivers or something like that. Said my installed hardware was ready to use. Noticed in device manager and network connections that Motorola USB networking driver #3 was installed. Under My computer, didn't see any new hard drives. I have RSD lite and the firmware you told me to get. RSD light shows my phone model, imei, software, ect and says that I am connected. But there has been no activity on my phone's screen. No Motorola logo, no menu's, nothing. I would feel more comfortable if I could pull my data off before I flash the phone as I have read horror stories of flashing gone wrong. Is there some way I can access my phone's memory since the computer recognizes it and backup my files before I flash?
RyanV-M said:
I connected the fastboot cable without a battery in the phone. Held power button, computer detected it. Said it had found an XT894 and Motorola Network drivers or something like that. Said my installed hardware was ready to use. Noticed in device manager and network connections that Motorola USB networking driver #3 was installed. Under My computer, didn't see any new hard drives. I have RSD lite and the firmware you told me to get. RSD light shows my phone model, imei, software, ect and says that I am connected. But there has been no activity on my phone's screen. No Motorola logo, no menu's, nothing. I would feel more comfortable if I could pull my data off before I flash the phone as I have read horror stories of flashing gone wrong. Is there some way I can access my phone's memory since the computer recognizes it and backup my files before I flash?
Click to expand...
Click to collapse
When the device is off just connect the device to your machine and it will boot to your rom thats it. It will do it automatically. No need turn it on yourself. If it wont boot then something is wrong with the rom. If that happens and you were running a custom rom and not stock go to safe strap if you had it installed and use that to boot back into stock rom slot. Now you have two scenarios you can use. Do the first one I wrote first. If you Have safestrap installed then do that if it wont boot. Dont forget to have to have the drivers installed for the device on your windows machine. On windows based systems you have to have the drivers installed installed before using rsd lite. Just in case I forgot to mention that.
My ROM and phone is stock
Another update: I'm trying to use ADB to backup my phones files before I flash. Here is what happened:
Sorry for the lack of updates, been busy. Anyways, I got adb installed, plugged in my phone, did adb>devices, didn't show up.I got the newest version of Motorola device managermanager and had it update. Plugged in my phone again, computer said it found an XT894 and Motorola USB networking device, told me to restart my computer. Restarted, tried to see if adb detected it, nothing. It shows up in my device manager under networking devices, it even says the location is an XT894. But adb still doesn't see it.
The weird part is that RSD can see my phone too along with device manager. I'm planning on flashing to see if I can unbrick my phone, however I want to try and backup my files on there just in case the flash wipes my phone.
Is there a way I can have my computer recognize my phone as a drive instead of a networking device so I can get my files?
Is there any way to get my data off my phone before I flash?
RyanV-M said:
My ROM and phone is stock
Another update: I'm trying to use ADB to backup my phones files before I flash. Here is what happened:
Sorry for the lack of updates, been busy. Anyways, I got adb installed, plugged in my phone, did adb>devices, didn't show up.I got the newest version of Motorola device managermanager and had it update. Plugged in my phone again, computer said it found an XT894 and Motorola USB networking device, told me to restart my computer. Restarted, tried to see if adb detected it, nothing. It shows up in my device manager under networking devices, it even says the location is an XT894. But adb still doesn't see it.
The weird part is that RSD can see my phone too along with device manager. I'm planning on flashing to see if I can unbrick my phone, however I want to try and backup my files on there just in case the flash wipes my phone.
Is there a way I can have my computer recognize my phone as a drive instead of a networking device so I can get my files?
Is there any way to get my data off my phone before I flash?
Click to expand...
Click to collapse
The only thing I can think of at the moment is safestrap If you had it installed before you bricked the device then you could try booting to safestrap and then mount device in safestrap and copy and paste all your internel sd stuff you want to keep. If you did not have safestrap installed then make sure you have correct drivers for device installed and try the adb command again and see if it reads. I'v been in your situation thats why once a month I now back new stuff up. When I had the s3 I bricked during bootloader unlock. Took me three days with an image file to get it to boot. Then I reflashed the stock and didnt need the image file any more. That was long time ago. i learned to back my stuff up after that. I just thought I would mention that just so you could have a food for thought. Also data will be lost is another reason to back stuff up.