So two key events happened with my phone - the replacement battery I ordered finally arrived, and I also crawled out from under a rock and flashed the ICS partition and pengus77's CM10.
I was advised to calibrate the replacement battery by charging it from 0 to 100 with the phone powered off. So I streamed a random high res youtube video to drain the battery as fast as possible, then powered off the phone and plugged it into a USB port on my work laptop (a HP Elitebook running Windows 7 Enterprise x64).
The phone started charging (battery animation screen appeared) - and then my laptop started to install drivers. A few minutes later, I got a windows BSOD - yes the blue screen of death, not the black screen on android.
I initially thought something else caused the BSOD, so I left the phone plugged into my laptop and rebooted. As soon as my laptop got past the "starting windows" screen, it BSODed again. Didn't even get to the "Please wait..." screen.
Tried to reboot again - BSOD before getting to the "Please wait..." screen. Finally I suspected my phone was the culprit, so I unplugged it. Another reboot - it successfully got to the "Please wait..." screen, and then I plugged in the phone (still off), triggering a BSOD in under 10 seconds, before I could even get the field to input my password.
Rebooted with the phone plugged in but powered on this time, and my laptop fully booted all the way, no BSODs. But if I powered off the phone and plugged it in, BSOD! Looks like I'll have to wait till I get home to my AC charger before I can calibrate this battery
This is quite strange - I never had any problems like this on the old GB partition, if I were to plug in my phone to the laptop with the phone powered off.
Has anyone else experienced such an issue before? If it helps, my work laptop is a corporate machine so I don't have admin access over many of its functions (though I can still install and uninstall programs like normal), and it's loaded to the brim with corporate bloatware, and it's possible these properties contributed to the BSOD.
Charging(forming) new battery via usb is never recommended to be honest
Most usb device don't provide enough power or stable voltages like charger designed for our phone
I personally never liked charging via usb(most usb hub's dont work properly also if they need to provide current to hungry device(our phone example)..
I have no prob's with that options and also using custom battery 1700mah...
I have no sod's on win but have read that people had problems and sods sometimes with usb charging...
It's hard to pinpoint exactly where problem lies,could be your low power usb on motherboard crashing your win or something else..
Hmm that sounds likely. I'm back home anyways and will use my AC charger to condition the battery.
I remember that on the old CM10 nightlies (before the call bug was fixed), the USB charger always BSODed my phone...
... an easy solution would be to start using a real operating system on your computer instead of windows
pengus77 said:
... an easy solution would be to start using a real operating system on your computer instead of windows
Click to expand...
Click to collapse
Believe me, I do - I use Linux as my main OS on my home computer, and only boot into Windows for games
However this is a corporate laptop that doesn't actually belong to me and I can't meddle with it like that.
My SM910T was working fine, and suddenly the screen froze for a few seconds, then blanked.
From that point on, the phone has done nothing but a brief vibration.
After a battery pull, starting up with 1) normal power switch 2) download startup 3) recovery startup 4) inserting USB cable
all result in the same: A short delay, a brief buzz from the vibration, which may repeat again every few seconds. The screen remains black.
When connected to a Windows computer with USB, the phone is enumerated. It shows up as these devices:
SAMSUNG_Android SAMSUNG Mobile USB Component,
trtlemo
Port #0004 SAMSUNG Android ADB Interface.
ADB does not work. The command "adb devices" returns the null list (List of devices attached)- it does not see any device attached.
Windows sees the phones internal file system as an MTP drive, and shows the file structure, but the files are not accessible.
ODIN sees there is a phone attached (it says <ID:0/004> Added!!)
What mode or state is the phone in, and what should be done to restore normal operation?
You may simply have a bad battery. Have your tried another?
Sent from my SM-N910T using Tapatalk
rcobourn said:
You may simply have a bad battery. Have your tried another?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I don't have another battery, but I can order one. I can't prove that the battery is not bad, but I don't think that is the issue. It runs the phone and is only down to 65 to 75% at the end of a day under normal use. At the time this problem started it was a bit lower, I think about 50%.
Even though the display was black and didn't show the charging logo, I left the phone on the charger with the battery inserted for 8 hours. It still didn't boot normally.
Assuming the phone had a hardware problem, I initiated a warranty replacement process. I wanted to see if any of my existing software tools could wipe the internal data before returning it so I tried a few (as described above). One I hadn't tried was Kies. I connected the phone to USB, and let it settle (USBdeview showed the phone connected and disconnected about 8 times before stabilizing). Then I ran Kies3, and saw the Emergency Recovery on the tools menu. I opened it to see if it would recognize the phone. The phone did not appear in the "list of devices requiring emergency recovery". However, after doing that, the phone booted normally. I don't know what Kies3 does, or if it did anything - maybe it was just a coincidence. But the screen activated, and the phone booted normally. The battery was charged, so it appears that charging does take place even if the system does not boot.
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.
hello everyone, I have an Honor 9 lite, without any mod, which has stopped working for a few days. Suddenly he rebooted and entered in bootloop, after about an hour he was definitely dead. Now I list the tests done:
- vol down + power => nothing
- vol up + power => nothing
- connection to the PC by holding down the power key and/or the key combinations mentioned above => the phone does not turn on but the PC recognizes a device
- I disassembled the smartphone, made a bridge between the testpoint frp and the gnd and the PC recognizes this new mode by showing a different name on "device management" of Windows
- after having disassembled it, I disconnected the battery (discharged) and replaced with a connector derived from an old battery and powered with an external 4V power supply, but even in this case the device does not turn on.
in all the tests carried out the device does not show any sign of life, the LED does not turn on and does not vibrate.
I would like to try the MRT tool after making the bridge in the FRP tespoint but first I have a question: reinstalling the software, will the internal memory be formatted?
Are there any methods to recover the data present in the internal memory?
Thanks in advance everyone for the help.