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.
Recently, I was using the GPS on my tbolt while driving, with a car charger, when I noticed that the battery icon had a question mark in it. A few minutes after arriving at my destination, the phone died, and will not charge or turn on. The orange charging icon does not turn on, regardless of what charger I use (official or otherwise). My girlfriends Incredible charges fine with the same charger. I took the phone to the store, and they didn't have any luck either, however, I didn't see them try another battery. They got me on the line with a rep to do a warranty return, and the new bolt should be here on Tuesday, and I have to ship my broken one back within 5 days after that.
The phone is rooted with CM7 on it. If they are able to turn it on, they will immediately see that it is rooted (custom splash, boot animation, etc..) My question is, has anyone had this issue? Is it fixable? Have you ever sent a rooted phone back under warranty? What happened? Should I try a new battery first? I'm not sure if the light should come on regardless of whether the battery works or not.
Any input is appreciated. I've read about people sending back rooted phones, but not for this issue.
It's more than likely a bad battery. Most Verizon reps are retarded when it comes to their phones (pretty sad right?) My girlfriend got her Eris's battery wet (a loooong time ago lol) and it got the question mark in the battery icon.
I don't think the light will come on without a battery.
As far as sending a rooted phone back, I'm not sure. If there is any way you could get your hands on another tbolt or rezound battery, I would try that.
Sent from my ADR6400L using xda premium
Try a different battery.
If you send back a rooted phone the worst that can happen is that you'll be billed full price for a new one.
Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
I guess this is an option also: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
mcappleman said:
Welp,
There's no doubt in my mind that my Galaxy S3 just hard bricked
Looking for some advice on what to do.
I've had the phone for 20 days, I've been running Beans Custom Stock ROM Build 10 for over a week I think?
And this is how it happened:
I started sending a few texts to one of my brothers, with "Go SMS" , and my phone around the time I hit send decided to switch to 4G (which it hardly does because it's only 1-2 bars where I am) , I then went into the basement and my phone then went to show 0 bars of 4G, then looked like it was going to switch to 3G but then the SMS application hung. I tried closing it, but it wouldn't, so I held down the power button and as the boot menu was coming up, that hung, so I pulled down the notifications bar and tried shutting off data, but then that hung. So, I had no choice but to pull the battery.
I left the battery out for a little while and then put it back in. Held the power button, and the device hung on the "Samsung Galaxy S III" first boot screen. I pulled the battery again and waited for a really long while and took my Micro SDXC out.
Tried to boot but power button does nothing. There's no signs off life!
Plugging it into a wall charger does nothing and I'm sure there's still charge in the battery because when it died it was around 20-30%.
Only sign of life I can get is when I plug it into my PC and then put the battery in. THE RED LIGHT TURNS ON.
:crying:
I have no idea what caused this, and I have no idea what to do!
Will Verizon cover this since it bricked without question and it's been under 30 days?
Or maybe Samsung will cover it?
Or because I rooted, I pretty much screwed myself?
I've never had anything like this happen before so I'm stumped...................HELP!!!!!!!!!!! I used to love my S III but now it's just a really nice paperweight.............. :crying:
Click to expand...
Click to collapse
Call verizon and they will send you an replacement. If its thats far gone theres no way they can check to see if its been modded.
Me too!!!!
Message removed
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
fr8cture said:
This happened to me after having mine for 3 days, i got mine replaced without a problem and i was rooted, cm10 custom kernel everything
Click to expand...
Click to collapse
But I've had it for 20 days now and their website says they don't allow returns or replacements after 14 days. Or is this different because it randomly died?
Also. I don't get insurance on my phones because they always would charge me $10 or more a month and then when the phone died they would charge half the cost of the phone just to get it replaced!
Honestly I think I may just send it to MobileTechVideos.........
Unless I still have a chance with Verizon. Hard decision............
I'm pretty sure the 14 day timeframe is for refunds on the purchase. Most electronics have some sort of manufacturer's warranty.
Have you tried to get it into download mode? volume down, then home, then power, Hold them all together until it boots into download mode? Do this while plugged in maybe?
samsung s 3
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
You really give your phone number out to strangers like that?
Sent from my SCH-I535 using Tapatalk 2
cmars said:
Take it to att ive done it a few times call cuctomer service tell them your on warranty hopefullt you bought this new from them they then will send you to repair center no one will no difference tell them it just crashed this doesnt seem like a rom problem its manufacture
email or text me [email protected] or 5105086739
Click to expand...
Click to collapse
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
mcappleman said:
Haha. Thanks!
Well, I ended up making a Google Voice account since my phone is dead and I called Verizon customer service. The first lady started having me go through the usual checklist like most companies do, I very nicely let her know that I've tried it all and I indeed know it's dead without explanation. She then sent me to someone higher up, we talked very briefly and she said it's covered under the manufacturer warranty, they're sending me a replacement for free. Only thing I paid for was a $12 upgrade to 1-day shipping!
I seriously was freaked out that I wasn't going to be able to get this replaced. Thankfully I can!
So, I guess, some advice to people that have hard bricked Galaxy S IIIs, CALL VERIZON BEFORE ANYTHING ELSE!
Thanks for the suggestions and help guys!
It's crazy how deep the brick went, the phone wouldn't even charge! Maybe I got a lemon? I hadn't even dropped or scratched it and I had 0 problems with unlocking/rooting it. I swear it was it hanging on trying to switch from 4G to 3G that killed it. Either way, stress is gone! phew! :fingers-crossed:
Click to expand...
Click to collapse
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
silver04v said:
So i didn't see it, but did you even try to get it into download mode?
Sent from my Synergized vzw S3!
Click to expand...
Click to collapse
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
mcappleman said:
It's hard bricked. Will not charge, no booting, and download or recovery mode won't work. Will not show any indication of life except for plugging it into a power source without the battery and then putting the battery in. If the red light comes on when you do that, it means it's hard bricked? Correct me if I'm wrong?
Click to expand...
Click to collapse
If you can't get into download mode then yea, most likely I guess or the battery died. I just didn't see that you said you tried to get into download mode.
Sent from my Synergized vzw S3!
Glad you got this fixed! Also i think its a 30 day replacement or swap for another phone if you don't like it. Thats what i was told when i got mine.
I bought a brand new Blaze a few days ago while vacationing in Florida. I neglected to check it out while i was there and Im home now (in Bermuda) checking it out for the first time and the phone wont boot! I popped the battery in and nothing happens when i try to power it on. So thinking the battery was dead, i plugged it in and now it just vibrates. It vibrates continuously every 2 seconds. buzzz...buzzz...buzzz...buzzz. The screen never powers on at all. Im guessing i have a bricked phone out of the box? Or is there a simple fix for this that i havent been able to find?
If i do return this, can it be returned to any authorized T-Mobile dealer? I wont be going back to Florida but i know someone who is visiting Boston next week.
Thanks
Jaa-Yoo said:
I bought a brand new Blaze a few days ago while vacationing in Florida. I neglected to check it out while i was there and Im home now (in Bermuda) checking it out for the first time and the phone wont boot! I popped the battery in and nothing happens when i try to power it on. So thinking the battery was dead, i plugged it in and now it just vibrates. It vibrates continuously every 2 seconds. buzzz...buzzz...buzzz...buzzz. The screen never powers on at all. Im guessing i have a bricked phone out of the box? Or is there a simple fix for this that i havent been able to find?
If i do return this, can it be returned to any authorized T-Mobile dealer? I wont be going back to Florida but i know someone who is visiting Boston next week.
Thanks
Click to expand...
Click to collapse
Try tmobile customer support they have gotten a lot better the last few years
I'm not a Dev, I just flash alot.
I'd return it personally. Same goes for any gadgets that fail before the initial return policy expires. Things happen, but I never liked that feeling of doubt that happens later, when something else goes wrong with the device. You'll be thinking, "I KNEW I should have exchanged this!"
Jaa-Yoo said:
I bought a brand new Blaze a few days ago while vacationing in Florida. I neglected to check it out while i was there and Im home now (in Bermuda) checking it out for the first time and the phone wont boot! I popped the battery in and nothing happens when i try to power it on. So thinking the battery was dead, i plugged it in and now it just vibrates. It vibrates continuously every 2 seconds. buzzz...buzzz...buzzz...buzzz. The screen never powers on at all. Im guessing i have a bricked phone out of the box? Or is there a simple fix for this that i havent been able to find?
If i do return this, can it be returned to any authorized T-Mobile dealer? I wont be going back to Florida but i know someone who is visiting Boston next week.
Thanks
Click to expand...
Click to collapse
Have you charged it fully? This is the default behavior if there isn't enough power to boot. Let it charge for 24 hours... then try again.
It vibrates like that when the device is plugged in and there's no battery detected or installed. My guess is the battery is defective or the orientation of the battery in the phone is incorrect (hey, it happens sometimes), or there is an obstruction preventing the pins in the phone from making contact with the battery or the pins don't properly align with the battery (defect with the phone or battery).
But I would agree that you should return it for another - especially if the pins aren't fully aligned with the battery when it's inserted.
Thanks guys, you were right, the battery was the culprit, it was dead flat.
I popped it into my universal charger, gave it a full charge and it was good to go, the phone booted and is working normally.
Thanks again.
My phone out of nowhere stopped being able to charge the battery while simultaneously not being able to send texts or calls but can use data?
I've been on the same rom for months with the same kernel for months, while driving home listening to google music my phone turned off and wouldn't turn on again...my 20% battery turned to zero now it cannot charge and everything else I said. I'm assuming it's hardware because literally nothing has changed in months
so how do I go about making it so I can return this piece of **** and get a new one?
Sorry for the rudeness and brevity but I'm ****ing pissed off a link to a guide or something would be awesome thank you guys.
Maybe a bad battery? A messed up battery could cause all of those issues. I'd try to get a new one and see if that helps.
So you can't boot the phone if it's plugged in? If you can, check your imei number and see what it says.
Sent from my SCH-I535 using Tapatalk 2