Heya! Im new on this site, but i got it recommended by a friend of mine. I have this mindbreaking problem. The thing is, a couple of nights ago, i came home from this party, and i was, very tired. To this party, i had brought my old phone instead of my brand new Desire S, so that no damage would be inflicted. So i removed the battery, to put my sim card in, while it was charging. The charging light was green tho' (dont know if that makes any difference). Now, the next morning, my phone went crazy, saying the sim card was full. And the phone was just generally really slow, not really responding and stuff. I restarted it, and then it said it had recovered from a system breakdown. Now my phone seems normal, but it brings me in such pain, not knowing wether my phone works as it should, or not. I could possibly know this since i only had my Desire S one day before the incident.
What to do?
Could anyone help me?
BTW i would've lovede og someone answered
willi0201 said:
BTW i would've lovede og someone answered
Click to expand...
Click to collapse
The green light indicated that the battery was charged to 100% so therefore didn't need further charging.
The error message that you received comes as a result of you removing the battery while the phone was party operational, in deep sleep mode. You need to disable the fast boot option (within Settings->power->Fast boot) in order to fully power it off.
I can't explain the phone slow behavior but unless the same thing has happened again since, I don't believe that this is anything to worry about.
I don't really understand the SIM card full comment, has the limit of SIM card contacts possibly been reached? Check the number of ocntacts that are stored on the SIM. Although with a phone like this contacts should ideally be stored in the cloud ie, Google/Facebook etc and not directly on the SIM, so I'd suggest moving them.
So, I'd do nothing and see what happens if anything again.
However if it continues, a factory reset would be my next move.
Sent from my HTC Desire S using XDA Premium App
Related
My inspire keeps powering off at ranodm times and has gotten worse. If its plugged into a power source it will stay on, but the second its pulled off theres a huge chance that it will just randomly power off. I've wiped the battery stats, factory rest a bunch of times, tried multiple roms and radios and can't find a solution. ANY HELP WOULD BE GREATLY APPRECIATED!!!!
See if ATT will give you a new battery.
Tx Redneck said:
See if ATT will give you a new battery.
Click to expand...
Click to collapse
I know it sounds like he's being an ass, but I think he's right. I have the exact same problem. Used CoreDroid, MIUI, & HoneySense 4 & 5 and they all randomly rebooted. I noticed that after I powered back on, the battery level would be significantly different. It got progressively worse as the battery level drops. Once I get to about 23%, it just turns off when I try to do anything. I speculate that the sudden increase in battery drain from the screen getting bright & the radio draws more current than the battery can provide.
To test, I got my phone to the point that it would turn off every time I booted it. It would show the homescreen & say that it had 18% battery. I then plugged it in to the USB charger & it works fine. I'll be replacing the battery ASAP.
this happend to me on CM7 and MIUI twice and the first time i just flashed off of CM7 and it stooped and on MIUI i just rebooted the phone while connected to the charger then when it was completely booted up i unplugged it and it was fine after that but that time it was caused by letting my battery die down and then i kept booting up my phone to completely deplete the battery and did this about 20 times and it wouldn't die so i just changed out batteries and when i booted and it would immediately power down like the battery was dead so thats when i plugged it in and powered on and it worked, and i know its not the battery because i have 4 batteries
cordell507 said:
this happend to me on CM7 and MIUI twice and the first time i just flashed off of CM7 and it stooped and on MIUI i just rebooted the phone while connected to the charger then when it was completely booted up i unplugged it and it was fine after that but that time it was caused by letting my battery die down and then i kept booting up my phone to completely deplete the battery and did this about 20 times and it wouldn't die so i just changed out batteries and when i booted and it would immediately power down like the battery was dead so thats when i plugged it in and powered on and it worked, and i know its not the battery because i have 4 batteries
Click to expand...
Click to collapse
Ok then, you "know" it's not the battery - so what is your speculation? Until I get the spare batteries I ordered today, I won't be able to fully test the battery theory. I can only say with certainty that the phone doesn't shutdown while plugged in.
I could also go along with another theory - The Thunderbolt got a recent OTA update that makes them randomly shutdown. Is it possible that a piece of that code made it into the new Gingerbread ROMs? I didn't note the issue running CoreDroid 6.4 (a GB build but the last to use EXT3 instead of EXT4 and was also released before the TB OTA update), but only after upgrading to 6.5. Could it be some finicky problem with EXT4?
meatrocket said:
Could it be some finicky problem with EXT4?
Click to expand...
Click to collapse
Actually, forget this part. I forgot I used HoneySense 4.0 with EXT3 & still had the random shutdown problem.
with it plugged in do a nandroid backup and then restore to stock then restore back with only restoring system and data
I know its not the battery because it will stay in CWM for several minutes and much longer than it does on without any random shutdowns. Going to try the return to stock and reflash method and post back.
Ok, so that I get this right, the test plan is to: flash back to stock, re-root & then reflash to a new ROM such as Coredroid 6.8? If that's what one of you are going to do, then I'll do it also so we can see if we get the same results.
Well, I actually downgraded to RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed, went through Bubby's One Click and the damned phone shutdown upon boot to the first image of Bubby's. I figured MAYBE something was wrong with Bubby's One Click as I had originally used the ACE hack kit.
I reverted back to RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed again & decided to use it for a minute to see if it shutdown and it DID!
There is either (A) a problem with my battery or (B) a problem with the charging system on my phone. This IS NOT a firmware/radio issue! It may be different for you, but I'm positive about my phone now. I'm going to wait until my new batteries come in on Wednesday and if it acts the same, I'll be replacing my phone under warranty. I should also note - I've never overclocked this phone, so I don't want anyone fear-mongering the N00BS about "see what overclocking will get you"!
Does yours stay on when its plugged in?
samftw said:
Does yours stay on when its plugged in?
Click to expand...
Click to collapse
Yes. I noticed the shutdowns started about 1½ to 2 weeks ago. It got more frequent as time went on. The phone is practically unusable now unless I leave it plugged in. I suspect that if it is indeed the battery, it may even start shutting down when plugged in since the phone will turn off if you remove the battery when it's plugged in. Just a hunch.
same exact story here totally bummed right now but at least i work for at&t so getting anew battery shouldnt be an issue. still a huge pain in my ass
samftw said:
same exact story here totally bummed right now but at least i work for at&t so getting anew battery shouldnt be an issue. still a huge pain in my ass
Click to expand...
Click to collapse
Well, bummer dude. I called AT&T and they said that the battery was covered under warranty & they'd be happy to send me one right out. The only problem was that they didn't have any in stock! They offered to credit my account with whatever I have to spend on replacing the battery myself. When I get the 2 batteries from Amazon & make sure they work, I'll get the credit for them applied to my account. It was only $25 for 2 batteries & charger shipped.
I called my local AT&T Corp stores to see if they had any batteries for the Inspire & they didn't either. Me thinks this widespread shortage of batteries could be indicative of a bigger problem.
WoW! Here's the feel-good part of this story....
As I posted earlier, AT&T service didn't have the battery to send me. I couldn't find a battery anywhere - I called the 2 AT&T Corp strores, BestBuy and Batteries +.
I went to the AT&T Corp store where I bought the phone & signed in for help. The girl came over to help as I was explaining to her what was happening & telling her that I wanted to take the battery out of her demo phone to make sure it was the battery. If it wasn't, then I could call service back & have them ship me a repalcement phone instead of having to wait until the batteries I ordered off of Amazon arrived.
She told me that she didn't want me to mess her floor phone up & offered to go in the back & get a phone to test with. She came back with a new battery still in the plastic. I popped it in and sure enough, it has been the battery! I told her thanks and that I felt a lot better knowing that it was indeed the battery.
She insisted that I keep the new battery since there were none to be found & she would "adjust" the phone she took the new battery from. I assume "adjust" is speak for "send it back as defective". I'm really positive about the whole experience, especially since she didn't have to do that at all. You can bet I'll be going back to that Corp store & buying from that rep when I'm ready to get my Samsung Galaxy S II!
I'm having the same problem I don't know why it's doing this
Sent from my HTC Inspire 4G™ using the XDA App.
King Askaba said:
I'm having the same problem I don't know why it's doing this
Sent from my HTC Inspire 4G™ using the XDA App.
Click to expand...
Click to collapse
Uh...did you read ANY of the thread or just post a reply? It seems rather obvious that there's a battery problem. Maybe you could do some of the same or similar testing we did to see if you have similar results?
The only thing I didn't say in all of this is that I got my phone on 2/14/11. So I've had it almost exactly 4 months before the problem really came up.
Hi,
My girlfriend has Desire S, from today's morning, when I call her or she calls me, she cannot hear anything, and neither do I, its completely dead, no answer... She said, that she cannot even hear an ringing, when my phone is ringing, so thats weird, and looks completely gone.
Today morning, when I took my phone(SGSII) off charger, it was dead and not turning on, for some reason, so I had to pull battery out and back, and then my SGSII started working again.
Thinking of this, I am afraid, that the speaker and microphone on her phone got permanently damaged by some overcharge during the night while it was on charger, since my phone got some issues at the morning too...
Any ideas? Her phone is nonrooted and in warranty, so we'll get that exchanged within warranty, if this proves to be the cause, but I am not really certain of it, would anyone here have similar experience?
Zheiko said:
Hi,
My girlfriend has Desire S, from today's morning, when I call her or she calls me, she cannot hear anything, and neither do I, its completely dead, no answer... She said, that she cannot even hear an ringing, when my phone is ringing, so thats weird, and looks completely gone.
Today morning, when I took my phone(SGSII) off charger, it was dead and not turning on, for some reason, so I had to pull battery out and back, and then my SGSII started working again.
Thinking of this, I am afraid, that the speaker and microphone on her phone got permanently damaged by some overcharge during the night while it was on charger, since my phone got some issues at the morning too...
Any ideas? Her phone is nonrooted and in warranty, so we'll get that exchanged within warranty, if this proves to be the cause, but I am not really certain of it, would anyone here have similar experience?
Click to expand...
Click to collapse
Have you tried a normal restart of your wife's phone (the Desire S) to see if the problem still persists?
Not that I can see it would help, but the next step would be to perform a full factory reset before testing again and then if no joy, returning the device under warranty for service with what sounds like a hardware problem.
Leaving these devices on charge all night is not ideal as it's a waste of electricity and risks over heating the device, you should only need a few hours to full charge the device.
Care should be taken not to remove the battery while the Desire S is running, unless you ultimately have to (ensure that Settings->Power->Fast Boot =OFF)
ben_pyett said:
Have you tried a normal restart of your wife's phone (the Desire S) to see if the problem still persists?
Not that I can see it would help, but the next step would be to perform a full factory reset before testing again and then if no joy, returning the device under warranty for service with what sounds like a hardware problem.
Leaving these devices on charge all night is not ideal as it's a waste of electricity and risks over heating the device, you should only need a few hours to full charge the device.
Care should be taken not to remove the battery while the Desire S is running, unless you ultimately have to (ensure that Settings->Power->Fast Boot =OFF)
Click to expand...
Click to collapse
Well, we are at work atm, so I was trying to guide her turning off the phone via SMS, she said she have done it. after arival home, I'll take a closer look on the phone, trying to remove battery completely and checking the FW status. I'll do factory reset using hboot, and check for updates... hopefuly this might help... If not, I'll probably be forced giving her my old Desire to play with till she gets back her beauty
Zheiko said:
Well, we are at work atm, so I was trying to guide her turning off the phone via SMS, she said she have done it. after arival home, I'll take a closer look on the phone, trying to remove battery completely and checking the FW status. I'll do factory reset using hboot, and check for updates... hopefuly this might help... If not, I'll probably be forced giving her my old Desire to play with till she gets back her beauty
Click to expand...
Click to collapse
(sorry to repeat)
Although, before you power down the Desire S do ensure that Settings->Power->Fast Boot =OFF
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
I guess the issue is with the battery itself. Try getting a new battery. I heard some guys experiencing the same and sorting things out replacing the battery....
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it
If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries
i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium
spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha
I agree. It still sounds like a battery issue.
I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.
I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App
Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.
If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!
The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.
Hi guys,
I recently ran into this problem after I woke one morning to my alarm clock blaring for about half an hour, the phone was pretty hot but not unbearably hot. I took out the battery and left the phone to cool down til trying to boot again, when I did the phone booted fine but it soon shut off again 5-10 seconds into loading into android. I assumed the heat knocked the charge out of the battery / something went wrong with the reading of the battery (as it read like 85%) so I just plugged it into the charger and left til it said it was full. It doesn't shut off by itself and works fine while on the charger regardless. But as soon as I unplug the phone dies within a few seconds. So I turned off the phone and let it charge overnight, woke again to the same issue and the battery reading 85% again. Before I booted back up though I tried the "Wipe Battery Stats" thing in CWM hoping that maybe it would fix it after I fully charged but it made no difference. Also I found that the phone is able to run off the charger when I severely underclock it to 250MHz but obviously it's too damn slow for every day use at that speed. As soon as I clocked it up to 480MHz it had the same issue again. I forgot to mention I was rooted with CWM, unlocked bootloader and on stock rom. After this I decided to revert to my pre-root back up rom from CWM and I still had the same issue.
The final thing that seems to make it work is removing the sim, I tried booting this morning without sim and the phone functions flawlessly even while under a heavy stress test without turning off. So I tried inserting another sim, this one not active. Issues start up again...
Any Ideas guys? Seems to me like if the phone is pulling "too much power" the phone auto shuts itself off. But then the SIM thing perplexes me, not really sure how it all affects.
Lastly, do you think I can still claim on my warranty? I've had this phone for just under a month and it's still in perfect condition... I really don't want to switch back to my chopped and screwed Motorola Flipout. But atleast that thing could handle the overheating pretty damn well. Also I didn't get this on contract I bought it outright from a reseller as a prepaid phone.
In the Netherlands, the warranty for a phone battery is set to six months by law, just contact HTC, and find out.
Sent from my HTC ChaCha with CM9 using XDA app.
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
metal man007 said:
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
Click to expand...
Click to collapse
SOLUTION:
Turns out my phone was stuck in a "boot loop"
Followed Champdood's instructions:
http://forum.xda-developers.com/showthread.php?t=2144101
Thanks everyone.