I'm new to this forum, and am in dire hopes that a workaround can be resolved for my issue. I've read a lot of posts here, and I've found people definitely know what they are doing here.
I have an XT894 (So I believe this is the right place).
I had this issue before, and I just ended up replacing the battery for a quick fix. The fact that it happened a second time makes me want to have a possible understanding of what I did, and if there's a workaround that doesn't involve me shelling out another 50$ for a new battery.
This is what had happened in the chain of events leading to this (Starting from JB Upgrade):
1) Rooted, and installed a generic Cyanogen mod on my original droid 4 (with Safestrap)
2) Randomly bricked, tried to take out battery without realizing that there were screws holding the flex cable in place.
3) Leaving incriminations out, I attained a second one.
4) Rooted it again using windows utility, and installed Liquidsmooth (Safestrap again)
5) Had the issue again, and bought a factory cable from a vendor in China. Was having a pile of driver issues throughout all this (got a new usb data cable, and used a specific port in the back of my pc that it liked.)
6) Factory cable booted it was able to get it back to normal while it was plugged in. Then swapped the battery the right way, used RSDLite, flashed Stock Rom, and got it working. Several times I've had to reflash.
7) Rooted again, safestrap, then flashed Liquidsmooth again. I had to reflash a few times with safestrap. I am using Rom slot 3 also.
Yesterday I decided to upgrade to the latest version of Liquidsmooth. I did not uninstall the operating system before flashing, and I'm pretty sure I completely ignored the fact the battery was under 1/4th charge.
So aside from all that, this is where I stand:
When using a standard data cable in the favored USB port of my PC, the screen stays blank, but a little green light appears in upper-left corner of the droid.
When using the factory cable in that port it boots, but will not charge. I was able to use AP Fastboot to reflash stock this way. I tried flashing the stock JB ROM with RSDLite initially, and it had an error on stage 6. But I was able to get it using the Windows Utility.
Now the issue is when plugged in the power charger it shows the Motorola logo, disappears, then again non-stop in an endless loop.
I have another charger coming on the way from Amazon (one usb, and one wall one), so that's going to be my next step.
If anyone has any little hidden secret or suggestion that will fix this problem that I am not aware of, please please by all means throw it out there! I would be eternally grateful.
the charge mode is software controlled, if the rom is not correct, battery will not charge
Sent from my XT862 using Tapatalk 2
Re: XT894 Charging Issue
Ah, that came to mind. Thanks for clarifying that. That's definitely a good sign.
What actions do you suggest I take to get that part of the phone back to normal again?
try wiping data in android recovery
Hard Reset (Alternate method)- DROID 4 by MOTOROLA - Verizon Wireless Support
if that doesn't fix
reflash stock rom, using .xml file and rsd lite
follow my instructions
How to Use RSD Lite to flash a .XML Stock Rom
also check for Motorola/windows Driver issues
Same issue still
I did the following:
Used RSD Lite, had a successful flash this time using 4.1.2_2.
Took it off factory cable (which always immediately powers off on removal, is this normal?)
Tried booting it off power, no go.
Plugged it into the charger, same issue.
Tried factory reset, couldn't get it passed the Android Andy.
After that, I tried flashing the 4.1.2_1 xml.
Had a successful flash.
Tried to get in recovery, and held both volume buttons. Didn't work.
Then I went into security settings and did a full wipe. Still didn't change anything.
Flashed same rom again, and then was able to get passed Android Andy by holding both volume buttons unlike last time where it was unresponsive.
I wiped the cache, and chose factory reset.
Powered it up again, and still had the same issue.
To clarify a bit on the factory cable: I've used it on 2 separate xt894s. Both devices always powered off on removal even on ones that were working fine. As I asked above: is that normal?
To recap again: it's showing the red circle with the M when plugged into the adapter. Then the screen goes blank. Then while the droid is in the charger, and I tap the power it up again it shows that, goes blank, and again in a non-stop loop. I've also tried holding the top button down as well with no different results.
The battery feels cold (I have air conditioning on), and when it's not plugged into anything the phone pretty much acts as if it is bricked. No red flashing light is shown on charger either, in fact no LED is lit up at all. The red blinking LED only shows on factory cable. I've tried two separate outlets in the room I'm currently in which power up other devices, and that's a no go.
The last time I bricked this phone didn't have that charger. Instead it had a USB charger with the adapter (was the default Verizon one). That one had the same results as the USB data cable I'm using now (a green light that did not flash). I had the battery completely removed, and the factory cable did the same thing as it's doing now.
Also around the time that this happened in Liquidsmooth, the icon showed that the power was charging (but the battery kept getting lower which makes me feel skeptical). Several days ago I left it in the charger for roughly two days as well.
I only have charged this phone with this current AC charger after the brick (I would link it, but the forum claims I don't have 10 posts). It does state that it is legitimately for XT894.
I'm going to leave it in that one for a few hours, and see if anything different happens. I never was able to get the M logo last time which is the big difference.
I ordered a second factory cable just to see what happens then.
Anyhow, does this seem more like a dead battery after my results, or is there another option I can try software wise? Or am I doing something incorrectly?
Related
Hey all, thanks for taking your time to read and possibly help me out with my problem. Yesterday I've tried rooting my droid in order to put cyanogen mod on it later. The reason I was interested in doing that was because I felt as droid was not working to it full potential and constantly crashing apps on me (browser, games, weather, etc). A friend of mine suggested cyanogen as he himself owns it. Being that I've did plenty of CFW on PS2, psp, xbox and mp3s/ipods, I thought there shouldn't be a hassle with this.
I followed the procedures listed on cyanogen's wiki page in order to complete the rooting process. But on the step where it asked to instal .sbf file trough RSD lite and wait till it says "pass" I've ran into trouble.
During the unpacking of that file to the phone using RSD lite the phone was undergoing several reboots, and after finally finishing the reboots on my PC screen in the RSD Lite window it showed 100% complete "please reboot the phone manually". I had no idea how to do that manually as the phone just kept going on and off by itself. (also for some reason it kept saying "error" force close/wait/send notice. But I thought it was probably just the process. After trying to reboot the phone a couple of times nothing worked. I didn't receive any "pass" signs on the droid screen.
I've got a little worried about the whole process and decided to shut the phone off and during that close the RSD Lite on my computer. Doing that made no further improvements for me. The phone just kept going on and off like crazy while in USB and not turning on at all while not plugged into either USB or AC. I've decided to go to recovery mode and just reset everything to stock as I was running out of time and had to get some sleep before work next day. After reseting the cache/data files I rebooted the phone but the same things kept happening to it. Now it was asking me to reconnect with gmail account and all that intro stuff. But the phone would always end up locking up and shutting off somewhere in the process of reconnecting the account.
Fast forward to today I've read that its possible to complete reset everything to stock version trough .sbf file once again. But now the problem consists of the phone not having enough batter life. (I'm not sure what the screen is called where the process of dumping .sbf trough RSD lite starts) but that screen keeps saying battery is too low to do anything with it. And mind me it has been charge for a very long time now in the AC adapter.
Now it also appears as the problem has worsened. The phone does not start up at all in either USB or without connection. It only starts up in AC adapter but then it shuts off in 2 minutes and back on and off , on and off. Recovery mode can't be accessed in any way, at least any way known to me. The black .sbf screen can only be accessed while the phone is not connected to anything but still keeps saying the battery is too low. And I've noticed the phone getting extremely hot during AC charge. (another small detail that sometimes when the phone does turn on and goes to home screen opening up the landscape view does not increase the length of the top (pull down) bar in horizontal view.
I've tried taking out both battery and sdcard and putting them back but no luck. I'm really lost as to what I can do next in order to fix this problem.
If you need any further information please let me know and thank you again for trying to help me!
I don't really see how you managed to get a fc with rsdlite.
Did you reboot your phone (turn off) then boot into usb recovery (power on while holding up, for the droid)?
Sent from my Droid using XDA App
I am by no means an expert and could be just wasting your time but in the absence of expert opinions something is better than nothing right? It sounds to me like maybe you have a bad battery that as luck would have it failed during the update/rewrite. Have you tried getting into recovery with the battery pulled running straight off the ac adapter? Hopefully you made a clockwork/nandroid backup before you started?
sent from a random hobo's droid on xda's app
I'm not an expert either, but having just successfully rooted my droid and installed cyanogen I feel the need to ask: did you hold up on the d-pad while RSD rebooted the phone the first time? If not then you needed to immediately restart the process.
I think you need to use a separate battery charger (meaning that charging battery without a phone) to charge the battery.
Sometimes, battery won't hold a charge when your phone is a brick.
BTW, it appears that you are having the same issue with mine.
(I can't post a URL because I am new here, but you can take a look at my article in this section, called "[S.O.S] A rare MILESTONE brick situation". )
I had the same problem (battery won't charge and phone won't start-up), I had to purchase a separate battery charger, and then flashed another SBF, to make the phone charging normal. (Although my phone is still a brick, but not a problem with battery. )
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
I take care to exit unused applications, etc, but this still occurs. In fact, I have tried rebooting to ensure nothing is left running in the background. Oddly, it occurs EVEN WHEN PLUGGED INTO THE CAR OR USB outlet... Most often this occurs when I'm using the device for navigation, so GPS, and DATA will be on. The notice has also popped up during other applications. It has happened when using LTE but also when LTE is disabled.
Is this something that everyone is experiencing? If you are, can you please post your Service provider, your SPECS, any mods, or if you have made any progress in stopping it. Lets see if we can track this down.
Mad Medik said:
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
Click to expand...
Click to collapse
That's strange. I've never seen a message like that. It doesn't sound like something native to Android / Sense, do you have any battery monitoring / power control apps installed that could be giving this message? How long does your phone last on a charge if you don't plug it in?
I've seen that error before. I wasn't using the USB cable and charger that came with my phone and that cable was damaged in the USB socket. Have you tried other plugs?
Sent from my HTC Raider X710e using XDA App
The reason you are probably seeing that on car or USB charger is due to then not proving the right amount of power. If you have the screen brightness set high and using navigation it uses quite a bit of power. Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Sent from my GT-I9000 using xda premium
Ive had that happen once when I was playing a really graphics intense game. I was over at a friends house and had it plugged into his computer to charge and was showing him how much better a game looked on my phone than his and it did that. I was using the 3 usb ports on the front of his tower, and he also had his phone and a headset plugged in that front hub as well, and since that hub is powered by one connection on the motherboard I just figured the 3 devices (mainly the 2 phones) were just drawing too much power at the time.
I have had it happen when I was playing a graphics intensive game while plugged into USB on my computer, but never when plugged into AC or car charger.
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
I would find someone with a vivid and try on it, maybe the battery is dead.
Sent from my HTC Vivid via Tapatalk
Mad Medik said:
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
Click to expand...
Click to collapse
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
rquiett said:
Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Click to expand...
Click to collapse
It looks like this is bang on. Apparantly computer USB ports for USB 1, 1.1 are minimum 200 mA with 500 mA recommended. Not sure about USB 2.0. Interestingly there is a proposal for USB 3.0 to allow for 20 Amps or more so you could easily power a laptop and other devices through a USB connection.
The HTC Holiday draws something more than 500 mA and presumably a max of 1 Amp as this is what the included HTC wall charger is rated for.
Anyhow, I guess I will have to pick up a new car charger, because the USB port in my car only pushes 500 mA max, and same for my current car charger.
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
jebise101 said:
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
Click to expand...
Click to collapse
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Mad Medik said:
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Click to expand...
Click to collapse
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Pirateghost said:
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
Click to expand...
Click to collapse
jebise101 said:
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Click to expand...
Click to collapse
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Mad Medik said:
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Click to expand...
Click to collapse
once you have done your recovery you dont need to do it again until you update the recovery with a newer version. its a one time thing, unless you relock stock RUU the device.
the ph39img.zip was configured for at&t vivid. you would probably need to modify it for any other holiday device.
if you are restoring from a backup, did you make sure and flash your boot.img from your backup first? otherwise you will be stuck at that HTC screen for a lot longer....just boot into HBOOT and flash the stock boot.img
Hello all,
I searched around, but didn't find anything quite like my issue so figured I'd create a new thread.
I work for a company that uses Galaxy Tabs for various purposes. One of our men brought back their VZW Galaxy Tab (SCH-i800) and it was in an infinite boot loop.
I went to recovery and attempted to do a full wipe. This did not work (partitions were all jacked up) so I couldn't get it fixed. I'm not sure if the guy tried to root the thing and broke it or what.
Anyway, I was attempting to root then fix the partitions (then was going to flash a stock unrooted rom) and ended up soft bricking it (Phone Icon -- /!\ -- Computer Icon). The issue I'm having is the only time that screen comes up is when the device is plugged into the wall. It turns on, then off, then on, then off. If I unplug the device, it shuts down with no way of bringing it back up. I've tried holding power for 5 minutes, the same amount of time with power + vol up and power + vol down. Plugging it into the computer's USB ports does not help either.
It's like the battery is drained but it won't charge when it's on the soft brick screen. I've had it plugged in to the wall for almost 6 hours now with no hope in sight. When it's plugged in, I feel heat on the back of the device like it would normally be charging. The AC adapter is also the standard warmth after a lengthy charge.
I was wondering if anybody has had similar issues with this device and if there is any way to correct it.
--- EDIT 8/10/2012 ---
Another thing of note is when the device is charging, I can power it down by holding power for a few seconds, but the Soft Brick screen pops back up almost immediately upon release of the button.
I cannot boot into recovery or the standard download mode even when it's plugged in.
As long as you can get the Phone ! PC screen, your'e good, because this screen IS as a download screen. Go to this screen and flash a known good ROM.
ableeker said:
As long as you can get the Phone ! PC screen, your'e good, because this screen IS as a download screen. Go to this screen and flash a known good ROM.
Click to expand...
Click to collapse
You must not have read the whole thing. Not a problem.
The only time I get the Phone ! PC screen is when it's plugged in to the wall. As soon as I unplug it, it goes away and the device won't start up no matter what I try.
When you connect the tab to the pc, is it recognized by Odin.
Sent from my GT-P1000
salahmed said:
When you connect the tab to the pc, is it recognized by Odin.
Sent from my GT-P1000
Click to expand...
Click to collapse
No... When the device is unplugged from the wall it is shut down and won't boot back to the download screen, recovery, nothing. It doesn't turn on. There are occasions where the download screen stays up but it appears to just be frozen. The computer doesn't recognize it and neither does Odin.
I left it plugged in when I left work on Friday... Going to see if charging for the weekend does anything.
MaskedDriver said:
No... When the device is unplugged from the wall it is shut down and won't boot back to the download screen, recovery, nothing. It doesn't turn on. There are occasions where the download screen stays up but it appears to just be frozen. The computer doesn't recognize it and neither does Odin.
I left it plugged in when I left work on Friday... Going to see if charging for the weekend does anything.
Click to expand...
Click to collapse
No dice.. still jacked.
I determined the following scenarios may have happened:
1) The battery died (bad battery) during a software update and messed up the partitions
2) The battery died (bad battery) while he attempted to (unauthorized) root or flash the device, messing up the partitions.
The only thing I'm sure of is the battery is fried so any kind of hacking I can do to the device are for naught. I was able to get it to connect to Odin this morning for about 3 minutes (after having it plugged in to the wall all weekend). During the flash it shut down again bricking it even worse. Now the device won't turn on when plugged in to the wall.
Thanks for the suggestions and help. I'm calling this a lost cause at this point. We're just swapping out the device for a new one. Once that's complete, I may tear the device down and try to do a reset on the main board to see if that does anything, though I doubt that's the case.
Right I had exactly the same problem as you (exactly the same symptoms) but I have now fixed my tablet.
Like you I got to the point where the Tablet had enough charge to actually unplug it and connect it to my PC where I then tried to flash a stock ROM using Odin. About three quarters of the way through flashing the stock ROM the tablet died, disconnected from Odin and I got a message in the task list in Odin advising me that the process had failed. Even weirder my PC did an emergency shut down and restarted in safe mode.
Anyway I tried it again but when I started my machine, once I'd logged onto my desktop I started up Odin as quickly as possibly, selected the .tar file and pressed start as quickly as possible....it worked and my tablet was flashed with a stock ROM. However my battery was still pretty much dead and the first time of charging once it had been flashed with the ROM took about 24hrs plugged in at a mains charger for the battery to reach 100%.
My point is persevere with it and you will fix it. I was at the point where I was about to send it off to be un-bricked but obviously I'm glad I didn't now.
It is a ***** of a brick though, this 'coma brick'.
I've been having these same issue with my friends i800 galaxy tab. Can you chime in and offer some advice?
Sent from my Galaxy Nexus using Tapatalk 2
same problem-solved
I was having the exact same issue. the device screen was completely black when plugged into the computer. I was just about to give up when, all of a sudden the device went to the boot error screen while plugged into my computer. Apparently, it must remain plugged into the computer for about 20-30 minutes. Once this screen appeared, I ran the Heimdall one-click unbrick utility, and like magic, my galaxy tab was working again. Give it a try, and good luck.
MaskedDriver said:
Hello all,
I searched around, but didn't find anything quite like my issue so figured I'd create a new thread.
I work for a company that uses Galaxy Tabs for various purposes. One of our men brought back their VZW Galaxy Tab (SCH-i800) and it was in an infinite boot loop.
I went to recovery and attempted to do a full wipe. This did not work (partitions were all jacked up) so I couldn't get it fixed. I'm not sure if the guy tried to root the thing and broke it or what.
Anyway, I was attempting to root then fix the partitions (then was going to flash a stock unrooted rom) and ended up soft bricking it (Phone Icon -- /!\ -- Computer Icon). The issue I'm having is the only time that screen comes up is when the device is plugged into the wall. It turns on, then off, then on, then off. If I unplug the device, it shuts down with no way of bringing it back up. I've tried holding power for 5 minutes, the same amount of time with power + vol up and power + vol down. Plugging it into the computer's USB ports does not help either.
It's like the battery is drained but it won't charge when it's on the soft brick screen. I've had it plugged in to the wall for almost 6 hours now with no hope in sight. When it's plugged in, I feel heat on the back of the device like it would normally be charging. The AC adapter is also the standard warmth after a lengthy charge.
I was wondering if anybody has had similar issues with this device and if there is any way to correct it.
--- EDIT 8/10/2012 ---
Another thing of note is when the device is charging, I can power it down by holding power for a few seconds, but the Soft Brick screen pops back up almost immediately upon release of the button.
I cannot boot into recovery or the standard download mode even when it's plugged in.
Click to expand...
Click to collapse
I am having this issue with my sch-i800.... phone /!\ pc screen only when plugged into the wall, and no recognition of it on the pc. Any way of fixing it?
Pl can anyone help me.....
I was on stock ICS and then i flashed Cm 10.1 Android 4.2.1 Unofficial rom which got stuck at boot loop for 5 hours...
Now my whole battery is down The phone is niether booting up nor going to Fastboot....
When i connect my wall charger to phone it goes to Fastboot and something like this appears :-
AP Fastboot Flash Mode (S) (Flash Failure)
0/OA.72
Battery Low
Cannot Program
Connect USB
Data Cable
On pressing VOL UP + VOL DOWN and inserting the charger it goes to Boot Selection Menu
BUT none of them work
1. On normal powerup it hangs on Motorola logo
2. On recovery it hangs on Motorola logo
3. Rest of the options don't work.........
I tried to charge the battery through "cut a cable" method but it didnt quite work......
CAN ANYONE PLEASE HELP ME BY TELLING WHAT CAN I DO?????????
shubhkirti1997 said:
Pl can anyone help me.....
I was on stock ICS and then i flashed Cm 10.1 Android 4.2.1 Unofficial rom which got stuck at boot loop for 5 hours...
Now my whole battery is down The phone is niether booting up nor going to Fastboot....
When i connect my wall charger to phone it goes to Fastboot and something like this appears :-
AP Fastboot Flash Mode (S) (Flash Failure)
0/OA.72
Battery Low
Cannot Program
Connect USB
Data Cable
On pressing VOL UP + VOL DOWN and inserting the charger it goes to Boot Selection Menu
BUT none of them work
1. On normal powerup it hangs on Motorola logo
2. On recovery it hangs on Motorola logo
3. Rest of the options don't work.........
I tried to charge the battery through "cut a cable" method but it didnt quite work......
CAN ANYONE PLEASE HELP ME BY TELLING WHAT CAN I DO?????????
Click to expand...
Click to collapse
Hi,
My best guess is that the battery died while you tried to do an FXZ recovery. If that was the case, I think I found a possible fix. Still there are a few other things to be weary of:
Did you:
Try to FXZ to anything other than 246 coming from 246?
Try to upgrade the stock ROM from 905 (GB) to 246 (ICS) without first FXZing to 905?
Try to upgrade to 246 from 905 or anything before 235 by using the 246 FXZ?
Any of those could have bricked your device. Keep in mind not to do those things as you read through this possible fix.
A little disclaimer: This idea is my best guess for how to fix your problem, but I take no responsibility if it breaks something or causes a problem. Please only proceed if you've FXZed your phone before and understand what I'm talking about... If you've been on an ICS Leak after 232 or on the ICS OTA, NEVER flash the 905 FXZ! If you haven't been on the ICS OTA or a Leak after 232 DO NOT flash the 246 FXZ! These instructions will most likely wipe your phone's internal storage/"SD card".
I suggest following this thread: http://forum.xda-developers.com/showthread.php?t=1549625 ( It's for the Droid RAZR so I'm not sure it will work, but the phones are very similar, so I'd try it. ) Stop at this point:
After a good charge up to 50% or so download the program called
Click to expand...
Click to collapse
I strongly suggest that you let it charge to 100% first. Then, if you were at one point successfully on 235-246, flash the 246 FXZ ( Found here: http://forum.xda-developers.com/showthread.php?t=1952040 ), if you never flashed anything post-232 flash the 905 FXZ ( Found here: https://docs.google.com/open?id=0B26Hj6_2TMNTZ256eV9QbWpBSTQ from this thread: http://forum.xda-developers.com/showthread.php?t=1771993 ). BE CAREFUL HERE! Let it finish completely.
This should return your phone to stock. Upgrade to 246 if you used the 905 FXZ and you should be all set. I'll leave rooting to you. Also make sure that if you try to flash Hashcode's 4.2.1 JB you do so in Safestrap 3.05 or higher ( http://forum.xda-developers.com/showthread.php?t=1391875 ) and do so in ROM-Slot 1 or you'll have issues ( Looks like he had to make a work-around to get it to boot that requires it to be in ROM-Slot 1 ). Do not flash his 4.2.1 ROM without Safestrap.
Let us know how it goes, and remember to thank vel0city for that post if it works ( I'd appreciate a thanks too though, ).
Good luck, I hope this fixes it,
jedi453
I'm not sure the battery will charge while bricked (could be wrong) . When that happens you need one of the factory cables that will power the phone regardless.
Can also get a charge from somebody else with a bionic.
Sent from my DROID BIONIC using xda app-developers app
Drunkula said:
I'm not sure the battery will charge while bricked (could be wrong) .
Click to expand...
Click to collapse
As far as I can tell you're right Drunkula, normally a special cable would be required to charge the phone, or as you suggest charging the battery separately of the broken phone. The thread I linked to however ( by vel0city, here: http://forum.xda-developers.com/showthread.php?t=1549625 ) is a manual work-around to bypass the requirement for a special cable. Although that thread refers to the RAZR, I would imagine the same could be true of the Bionic.
I had the same problem i went to a battery store and bought an external batter charger (a little clip) and everything was great
Sent from my DROID BIONIC using xda app-developers app
Buy a factory cable or factory cable adapter from team black hat. It works just fine. You will be able to fast boot the phone back to stock
Sent from my XT894 running ICS
shubhkirti1997 said:
Pl can anyone help me.....
I was on stock ICS and then i flashed Cm 10.1 Android 4.2.1 Unofficial rom which got stuck at boot loop for 5 hours...
Now my whole battery is down The phone is niether booting up nor going to Fastboot....
When i connect my wall charger to phone it goes to Fastboot and something like this appears :-
AP Fastboot Flash Mode (S) (Flash Failure)
0/OA.72
Battery Low
Cannot Program
Connect USB
Data Cable
On pressing VOL UP + VOL DOWN and inserting the charger it goes to Boot Selection Menu
BUT none of them work
1. On normal powerup it hangs on Motorola logo
2. On recovery it hangs on Motorola logo
3. Rest of the options don't work.........
I tried to charge the battery through "cut a cable" method but it didnt quite work......
CAN ANYONE PLEASE HELP ME BY TELLING WHAT CAN I DO?????????
Click to expand...
Click to collapse
heres what you do OP.
find an old USB charging cable. splice it open until you see two wires. spice those wires (red and black i believe)
open your case and put the leads of each wire against the terminals where the battery goes
match RED with the + icon on the battery and the BLACK with the - icon
you need to be patient it takes a few times before you get the leads touching correctly while inserting the battery.
then simply plug it into USB and boot into fastboot. you will see BATTERY OK.
from there you must flash whatever firmware to get the phone back to stock.
i've done what you've done before, trying to flash flash flash and then the battery dies and u cant even boot past moto logo.
seems as though the black fastbook/flash screen eats battery life
this works and its very simple!!! good luck!
Be Careful About Physical Modifications!
paradoxed said:
heres what you do OP.
find an old USB charging cable. splice it open until you see two wires. spice those wires (red and black i believe)
open your case and put the leads of each wire against the terminals where the battery goes
match RED with the + icon on the battery and the BLACK with the - icon
you need to be patient it takes a few times before you get the leads touching correctly while inserting the battery.
then simply plug it into USB and boot into fastboot. you will see BATTERY OK.
from there you must flash whatever firmware to get the phone back to stock.
i've done what you've done before, trying to flash flash flash and then the battery dies and u cant even boot past moto logo.
seems as though the black fastbook/flash screen eats battery life
this works and its very simple!!! good luck!
Click to expand...
Click to collapse
I would not recommend this option. While it may work, it's very possible that it may damage your phone. For those that disagree or don't understand why I would say this, my reasoning is that USB provides 5 Volts at usually up to 500 mA standard, while a battery would provide at max 3.7 Volts at a higher current. This is simultaneously giving the phone too high a voltage ( BAD, can cause permanent hardware damage! ) and possibly not providing enough current ( The flash could fail, and you'll be stuck again ). There is also the possibility of shorting ( inadvertently connecting ) two pins/terminals/connections in the phone with the wire from the USB cable.
In short: I strongly suggest not directly connection a USB cable to the phones battery terminals.
I apologize to paradoxed for the blunt response, but the inherent risks outweigh the possible benefits. ( Note to shubhkirti1997: it sounds like your phone is "soft-bricked" which in my understanding means the software is not working correctly ( So it may be possible to fix it without gutting it ), attempting to interface a USB cable with the battery connectors may make it "hard-bricked", as in the Hardware is broken, and no amount of flashing or software modding/fixing will fix a hard-bricked phone.
Good luck shubhkirti1997, but be weary of any possible solution that involves physically modding your phone until you're sure that there are no good alternatives.
jedi453
jedi453 said:
I would not recommend this option. While it may work, it's very possible that it may damage your phone. For those that disagree or don't understand why I would say this, my reasoning is that USB provides 5 Volts at usually up to 500 mA standard, while a battery would provide at max 3.7 Volts at a higher current. This is simultaneously giving the phone too high a voltage ( BAD, can cause permanent hardware damage! ) and possibly not providing enough current ( The flash could fail, and you'll be stuck again ). There is also the possibility of shorting ( inadvertently connecting ) two pins/terminals/connections in the phone with the wire from the USB cable.
In short: I strongly suggest not directly connection a USB cable to the phones battery terminals.
I apologize to paradoxed for the blunt response, but the inherent risks outweigh the possible benefits. ( Note to shubhkirti1997: it sounds like your phone is "soft-bricked" which in my understanding means the software is not working correctly ( So it may be possible to fix it without gutting it ), attempting to interface a USB cable with the battery connectors may make it "hard-bricked", as in the Hardware is broken, and no amount of flashing or software modding/fixing will fix a hard-bricked phone.
Good luck shubhkirti1997, but be weary of any possible solution that involves physically modding your phone until you're sure that there are no good alternatives.
jedi453
Click to expand...
Click to collapse
^^^ This. For people who have a good head for electronic devices, this would be an easy task - but for someone not well versed in electronics, this could be disastrous. A single misplacement of the wires when inserting the battery could damage either battery or phone or both permanently.
jedi's advice is sound - charge the battery externally (I bought my BIONIC from CostCo, they provided an extra battery and an external battery charger) using an external battery charger, or borrow a friend's battery, or buy an extended battery (should come with 50% charge, which is around 65-70% capacity of the stock battery).
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
And you could always just get the Factory Adapter and never have to worry about a flashing/power issue again...just sayin'.
cellzealot said:
And you could always just get the Factory Adapter and never have to worry about a flashing/power issue again...just sayin'.
Click to expand...
Click to collapse
Heyas, cz, ltns....
Yeah, it was mentioned in a previous post in the thread to do that. Speaking of which, I need to order the adapter, if they're back in stock
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
I really try very hard to respect the rules on XDA and don't make self promotional posts for TBH, but it's hard sometimes not to especially in view of the litany of items you suggested there. You can purchase a $10 Factory Adapter and never be concerned about the issue ever again for any Motorola device regardless if it has a removeable or non removeable battery or no battery at all!
And we will never be out of stock again...trust me!
Lol, I wasn't even thinking about it from the perspective of self promotion. I just knew an earlier post had suggested getting the Factory Cable already.
Until you mentioned it, I had forgotten that you guys had made the adapter too. Going to buy one *right now*.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
Please help on my droid bionic
All, please help !!!!
I bought a droid bionic on ebay (seller didn't mention that the software is corrupted) now tired to install ICS using RSD 5.7, it installed correctly, but the phone boots up and gets stuck on the "Droid" screen. Nothing happens from there. I can go to AP boot and/or recovery but can't do anything about it. Please help !!!! Searched the web for two days but no solution. I loaded the following file with RSD, downloaded from different site and tried atleast 5 times.
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip
rahm0809 said:
All, please help !!!!
I bought a droid bionic on ebay (seller didn't mention that the software is corrupted) now tired to install ICS using RSD 5.7, it installed correctly, but the phone boots up and gets stuck on the "Droid" screen. Nothing happens from there. I can go to AP boot and/or recovery but can't do anything about it. Please help !!!! Searched the web for two days but no solution. I loaded the following file with RSD, downloaded from different site and tried atleast 5 times.
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip
Click to expand...
Click to collapse
Try to factory reset the phone, you can do that by booting in recovery mode.
Sent from my XT925 using Tapatalk 2
Got my bionic repaired
ok guyz i after all restored my droid bionic back to its state..........
WHAT I DID
i took a red neck USB charger and charged my battery for about 1 hour it it got booted up
then i flashed ics using RSD lite 5.7
NOW ITS WORKING FINE THANX EVERYONE FOR YOUR HELP
I know that this thread is pretty old, but my question lies with my droid bionic being hard brick. What I read from the OP wasn't a hard brick and appeared only to be a soft brick. My issue is that I accidentally flash the wrong firmware into my phone following a post about turning the droid bionic into a global phone that I could use any sim with from any network. it was working properly but had some issues with the data network. back to the topic. I flashed the firmware using rsd but since it was the wrong one my system crash and no longer boots at all, the battery at the time was almost 100% so i know it wasn't because of the battery. I even made sure that I check with a battery charger I bought for like 5 bucks. My question is, is it possible to un hard brick the phone and restore it back to working again? I read around about using the JTag method but couldn't find too much detail about the subject. and each article relating to hard brick phones were specific only to that phone. I've search all over XDA to find out if there are any threads concerning this issue and even posted my own in hopes of finding a solution to this issue.
New to the bionic. Not my main phone.
Not new to flashing but mostly Samsung stuff.
Read up as much as i could before flashing.
Had upgraded this bionic to ics and was working ok , tried it couple different ics ROMs, was in process of upgrading to jellybean,, battery was over 80% @start,
Something happened,,, seemed as though battery died early in process... Black screen,,, can't get to boot anymore.
At best i can only get it to show a white ( low battery?) Led light in upper right corner
I have the factory battery charger dock.
Charged many times and retried many times with no luck... Bought a different but used battery, same thing... They show as needing and taking a charge,, light goes from Orange to Green.
Even bought a team Black Hat factory adapter to supposedly allow me to get past this, but i still have same results.
Although can't get it to show white led on phone while using adapter at all
Even tried a hacked USB cable taped to the battery.
Any suggestions, what am i missing?
Can't get into fast boot, pc doesn't recognize
Bricked right now
.
With the TBH Factory Adapter connected it should flash a white light once immediately when connected and then the phone should boot up.
If the OS is corrupt then it will go to the fastboot bootloader screen and can be flashed with a full XML.zip using RSD Lite or manually with fastboot.
If the bootloader is corrupt it should do the single white flash and then cycle through attempts to load the OMAP Flash interface in Windows with repeated up/down beeps while connected.
This can be fixed using Linux and the omapflash-lnx binary if we had the bootloader repair kits for the latest bootloader revision, but the only repair kits I have seen in the wild are for the older ICS builds.
If nothing happens at all when the TBH adapter is connected, then you have a hardware damaged device or true "brick".
@cellzealot thanks for the great explanation. Was kinda hoping it would let me do these things...
I'll go back n double check, but I'm pretty sure only white light i could get is ~ without ~ the adapter :banghead: