Hi, this morning I was charging my phone, received a call, and phone shut off. It literally did a single ring and then off. I went to turn on the phone, thinking it was just overheated, noting it was cool to the touch. When I went to turn the phone on, it vibrated on boot like normal, except nothing was displayed on the screen. Further waiting (approximately 2 minutes) led to nothing. I attempted to power on again, with the same vibrate, same thing. I removed the charger, then the battery for about a minute. Replace battery, left out charger, same thing. Replace charger, same thing. I had been running AOKP fine previously. Before that I had been running stock AT&T 4.1.1 . I followed Tasks' instructions in his post, I'm not new to this process. I've been following him since the S2 (SGH-I777), never had any kind of brick at all. I've also compiled CM and AOKP myself before and am not new by any means to linux. But I have no clue what just happened here and no kind of recovery or bootloader is available from what I can see on the phone and through ADB. It simply will not power on. I don't have a multimeter to rule out the battery but it seems unlikely to me that in just under 8 months of use the battery died on me. I'm not a heavy user, and typically get 3 days use out of a single charge. Anyone heard anything on the grapevine?
EDIT: I put the wrong release date in the title when I went to look at his releases. It's the 7/9/2013 release.
EDIT #2: I pulled out the SIM card to place in a backup phone and I tried booting the phone again. It started up, got to the loading screen, shut off, and now its back where it was. Considering playing with my SIM in the phone to see if I can trigger anymore activity.
EDIT #3: Success, flipping the SIM seemed to trigger something, I was able to put the phone in Download successfully. Flashing new recovery now, stay tuned.
EDIT #4: When I was able to boot the phone after flashing Jiangyi's AIO (From tasks post). I immediately booted into recovery, flashed 7/20b and 7/14 gapps, looking good so far.
Related
Last night I had dropped my phone from about a foot on a sitting-swing and it hit the ground. I have the black case from the sprint store on it. After that I attempted to turn it on and it just got stuck on Samsung loading screen with the genocide 2.0 logo below it, it then proceeded to be stuck there and eventually rebooted, this never seemed to end. When I attempted to plug it in to charge it the battery charging icon appeared but just has the loading symbol inside of it frozen, after many battery pulls and attempted clockwork-recovery boots failing I decided to go to bed. When I awake I went and tried to turn on my phone which immediately booted up into clockwork recover, fearing for my phones safety I backed everything up on it and then rebooted it. It seemed to work fine! It came on flawlessly and worked well. Throughout the day the battery seemed to drain extremely fast and then eventually died, having just gotten home I have found that the same thing is happening and it won't even charge.
Re flash the ROM then flash journaling on zip right after you flash the ROM then re boot & download you're apps fresh cuz you're data might be corrupted! Hit the thanks button if I've helped in any way! ;-)
Sent from my SPH-D700 using xda premium
I flashed back to stock rom to see if it would turn on, same thing happens, and I don't know if this is significant or not but when my phone boots up the buttons light up, then turn off, then back on again and stay on until the phone reboots itself or the battery is pulled.
EDIT: I have a strong feeling it's my physical battery that is causing the issues because it was working completely fine earlier yesterday.
Try booting in safe mode by holding power and the physical menu button until the phone gets to the lockscreen... Im curious to see if it helps because safe mode might help us get out of soft bricks? I wanna test this theory...
No it does not work, just get stuck at the Samsung loading screen. I don't honestly believe this is a software brick either because of the way it's acting, as I said in my above post I believe it's the physical battery and will probably be going to get it replaced soon
Hello,
today I was fooling around with my Phone, flashing stuff etc... =D
I wanted to flash the touch version of CWM and decided to delet everything and install my phone completely new without all the junk. So I made a Titanium Backup and than I wanted to copy the backup to my PC. There the problems started, I chose the Titanium folder and wanted to copy it to my PC but just the folder was copied without the contents. I didn't get it to work. Then suddently my PC couldnÄt recognize my GNex anymore.
Because of that I just deleted everything with a Filemanager and just left the Titanium Backup Folder on the SD, a ROM (AOKP b27), Francos.Kernel and a Boot Animation zip.
So then I went into Fastboot mode and installed the new CWM with the GNex Toolkit and than flashed everything without problems.
After rebooting I plugged my Phone into the Wall Charger (the one supplied with the GNex) and had to discover, that it wouldn't charge at all. So now I can't charge it while the phone is on, I can only charge it while it's off?! And while it's off the screen shows the batteryicon with the flash inside and than for 5 secs it show an animaton of the battery filling up, and then the screen stays black for 1-2 secs and the icon with the flash comes again; is this the normal animation? I think I can remeber it just showing the icon with the flash once and then just the battery charging right?
So I googled a bit about this problem and I don't think it has something to do with the software; so can anyone give me some advise? Is it broken, do I have to send it in?! =(
Sounds like something is up with your ROM or kernel. Have you tried performing a nandroid backup and flashing AOKP?
Well, I did install everything new, ROM & Kernel because I thought that could help but it didn't
Edit:
Just now: Phone was charing while off, I booted it up and in the Battery Settings Screen there was the message " not being charged", I unplugged the phone and the message changed to "discharging" then I plugged it in again and suddently it was charging, unplugged again and plugged in again but now it just stays at discharging
Could the battery be defectiv?
Edit2:
Ok, so now I installed 4.0.2 Stock Google with Gnex Tollkit and it seems to be working, so porbably something witht he rom...strange I ask myself what could have done it?
Ok I need help!
So my problem is not yet solved...
Now my phone charges while on but when I disconnect it it's still charing... The symbol on the battery icon in the notification bar shows the little flash and in Batterysettings the graph keeps reseting the time every 10-20 secs...
So basically the phone - even not on the charger - keeos showing every 10-20 secs that it's charging and than it's not and this keeps going...
I think it must be a hardware problem with the battery because I already flashed a completly new rom and kernel etc....
Anyone suggestions?
Edit: Oh something that I noticed too...since it keeps charing and discharging my screen goes on everytime it "charges"...
lukasb9000 said:
Ok I need help!
So my problem is not yet solved...
Now my phone charges while on but when I disconnect it it's still charing... The symbol on the battery icon in the notification bar shows the little flash and in Batterysettings the graph keeps reseting the time every 10-20 secs...
So basically the phone - even not on the charger - keeos showing every 10-20 secs that it's charging and than it's not and this keeps going...
I think it must be a hardware problem with the battery because I already flashed a completly new rom and kernel etc....
Anyone suggestions?
Edit: Oh something that I noticed too...since it keeps charing and discharging my screen goes on everytime it "charges"...
Click to expand...
Click to collapse
Help ! got exactly the same problem on my GN =(
Have the same problem, heres a very helpful response to a thread i started:
http://forum.xda-developers.com/showthread.php?p=23411891#post23411891
I had this same exact problem two days ago. After a lot of googling and changing roms and going back to stock I brought it to Verizon.
The woman there basically told me in not so many words that if it's charging and not dying immediately I should try living with it, which I told her was unacceptable. I said "you can clearly see that it shows it's charging right now. While the phone thinks it's charging, it doesn't go into proper sleep mode, and therefore the battery drains much faster. Additionally, I don't know when it's charging for real or just saying it's charging."
She went into the back for a minute and came back out and offered to ship me one. I just got a "certified like new" shipped to me next day (I have the insurance on the phone) and it seems perfectly fine so far. Updated to 4.04 and restored with Titanium Backup.
From everything I've read it looks like a hardware problem and won't be fixed with software. You may temporarily fix it by leaving the battery out for like 30-40 seconds, but then when you go to plug it in you're going to introduce the problem again.
I would bring it into Verizon and tell them it's unacceptable, and demand they replace it. Good luck.
I have the SGH-T999 running the RC2 version of CM 10.1. I flashed Mako Kernel this morning to try it out and when I rebooted the phone after the flash the screen went dark. I figured there was just a reboot issue and held down the power button but nothing happened. I pulled the battery and put it back in, tried to reboot, nothing. No matter what I do the phone does not turn on now...no booting into recovery, no booting into download mode, nothing at all.
Some interesting things to note:
-When I plug the phone into an outlet WITHOUT the battery being in, the notification light turns on in a red color. When you put the battery in while it's in this state the light remains illuminated.
-I left the battery out of the phone for about 30 minutes and when I put it back in (while the phone was unplugged) the camera flash blinked very quickly.
-My GF has the same phone and all of her stuff is working fine. I tried out her battery but the phone still won't turn on (thus eliminating it being a battery issue).
I'm at a loss...I've owned several top-of-the-line Android phones and have rooted/customized them all and have never bricked anything ever. Is this phone truly done for??
strippedman said:
I have the SGH-T999 running the RC2 version of CM 10.1. I flashed Mako Kernel this morning to try it out and when I rebooted the phone after the flash the screen went dark. I figured there was just a reboot issue and held down the power button but nothing happened. I pulled the battery and put it back in, tried to reboot, nothing. No matter what I do the phone does not turn on now...no booting into recovery, no booting into download mode, nothing at all.
Some interesting things to note:
I'm at a loss...I've owned several top-of-the-line Android phones and have rooted/customized them all and have never bricked anything ever. Is this phone truly done for??
Click to expand...
Click to collapse
you flashed a kernel for the Galaxy Nexus if I'm not mistaken... You bricked, nothing wrong with the phones hardware. Jtag is your option now.
So I recently installed CM 10.1.2 on my S3, and everything worked perfectly for a few days. Yesterday though, my phone started acting strangely (lag when turning screen off, registering phantom input, etc) and began rebooting every few minutes. At some point, it ran out of battery - and now I can no longer boot past the CM loading wheel screen.
I can't boot to recovery, and I don't think my phone is taking charge (from my computer or a wall outlet), and the farthest I can get is the loading wheel - sometimes it only gets as far as displaying the Samsung logo, or the Galaxy S3 screen with the android dude at the bottom.
I'm still covered under warranty, and would love to take it to the store for a replacement (I've had battery issues prior to this), but the fact that it can get to the CM loading wheel means that they might figure out that I've rooted and whatnot. But I can't get to recovery to flash a stock image, so...what can I do?
vortexface said:
So I recently installed CM 10.1.2 on my S3, and everything worked perfectly for a few days. Yesterday though, my phone started acting strangely (lag when turning screen off, registering phantom input, etc) and began rebooting every few minutes. At some point, it ran out of battery - and now I can no longer boot past the CM loading wheel screen.
I can't boot to recovery, and I don't think my phone is taking charge (from my computer or a wall outlet), and the farthest I can get is the loading wheel - sometimes it only gets as far as displaying the Samsung logo, or the Galaxy S3 screen with the android dude at the bottom.
I'm still covered under warranty, and would love to take it to the store for a replacement (I've had battery issues prior to this), but the fact that it can get to the CM loading wheel means that they might figure out that I've rooted and whatnot. But I can't get to recovery to flash a stock image, so...what can I do?
Click to expand...
Click to collapse
Your best shot is to either borrow someone's S3 battery or buy a battery pack. Use that to restore your phone back to stock (unroot) and then you can go to the store for replacement.
alltechinside said:
Your best shot is to either borrow someone's S3 battery or buy a battery pack. Use that to restore your phone back to stock (unroot) and then you can go to the store for replacement.
Click to expand...
Click to collapse
So turns out battery isn't the issue, I used a wall charger to get it to full charge. I can get it to the download mode confirmation screen, and can press volume up to confirm - but my phone reboots soon after that.
Recovery isn't really possible either, I can see the blue text in the upper right but my phone reboots after that as well.
My phone will often show an empty battery icon with a little refresh icon in the middle; does this indicate that it doesn't see the battery as charged (even though it is)?
vortexface said:
So turns out battery isn't the issue, I used a wall charger to get it to full charge. I can get it to the download mode confirmation screen, and can press volume up to confirm - but my phone reboots soon after that.
Recovery isn't really possible either, I can see the blue text in the upper right but my phone reboots after that as well.
My phone will often show an empty battery icon with a little refresh icon in the middle; does this indicate that it doesn't see the battery as charged (even though it is)?
Click to expand...
Click to collapse
My phone started having the same problem yesterday and I tried my friends battery but it still doesn't work.
mtmodi said:
My phone started having the same problem yesterday and I tried my friends battery but it still doesn't work.
Click to expand...
Click to collapse
Yeah I've been doing some research into the issue...
I've noticed that my phone automatically boots when I put the battery in, and that it'll do a quick vibrate when plugged in to a power source (outlet or computer) but won't turn on.
Apparently the phone isn't supposed to boot automatically when the battery is put in, and this could be the source of the random reboots - I think if I can get the rebooting under control, I'll be able to get into download mode and fix it all. But I'm not sure how to do that. Maybe the power button has gone bad, as it also doesn't usually respond when I try to use it to turn on.
If there is a problem with the power button, does anyone have any ideas on how to fix it?
vortexface said:
Yeah I've been doing some research into the issue...
I've noticed that my phone automatically boots when I put the battery in, and that it'll do a quick vibrate when plugged in to a power source (outlet or computer) but won't turn on.
Apparently the phone isn't supposed to boot automatically when the battery is put in, and this could be the source of the random reboots - I think if I can get the rebooting under control, I'll be able to get into download mode and fix it all. But I'm not sure how to do that. Maybe the power button has gone bad, as it also doesn't usually respond when I try to use it to turn on.
If there is a problem with the power button, does anyone have any ideas on how to fix it?
Click to expand...
Click to collapse
Mine does the exact same thing where I have to pull the battery and when I put it back in it automatically starts up and when I go to download or recovery it turns off before I can do anything
Sounds like power button issue.
I was having the same issues (random reboots, boot loop, powering on when battery put in, reboots in download mode and recovery)
This is not an easy fix. I ended up pulling the power button out and just setting my screen to time out after 15 seconds. Sucks but it works now.
If I ever need to turn off or hard reboot, I stick a pin in the power button hole and push down on the button.
Really turning me off on purchasing future Samsung phones
Sent from my SAMSUNG-SGH-I747 using xda premium
The power button is a common issue for these phones.
I run a M.O.A.R. stock 4.2 rom on my Sprint GS3 SPH-L710 (that is out of warranty). Yesterday, I was scrolling through facebook when my phone spontaneously rebooted. It didn't lag, or slow, or start to not respond. I was scrolling through my feed, and suddenly it was going through the boot screens. Except it wasn't just a reboot, it went into a boot loop.
I let it reboot maybe four or five times before pulling the battery. After a few minutes, I started it up again and it was fine. It operated normally for the next couple of hours until I felt it vibrate in my pocket, and when I pulled it out I found it had went into a boot loop again. Once again, I pulled the battery.
But this time, the phone wouldn't power up. I couldn't get it to power up, go into recovery mode, download, anything. Every button combination I tried produced no response. I tried using a different battery, didn't work. I tried charging my phone for a few hours (even though my phone was >75% when this happened) and even the battery indicator screen didn't show when I pressed the home button.
I searched for possible fixes, but I couldn't find any post or thread that was similar enough to the situation I'm in. I'm 99% sure it's not Sudden Death Syndrome, and that's about all I've found.
Anyway, I need help. What can I do (if anything) to make my phone work again?
sircharlieg said:
I run a M.O.A.R. stock 4.2 rom on my Sprint GS3 SPH-L710 (that is out of warranty). Yesterday, I was scrolling through facebook when my phone spontaneously rebooted. It didn't lag, or slow, or start to not respond. I was scrolling through my feed, and suddenly it was going through the boot screens. Except it wasn't just a reboot, it went into a boot loop.
I let it reboot maybe four or five times before pulling the battery. After a few minutes, I started it up again and it was fine. It operated normally for the next couple of hours until I felt it vibrate in my pocket, and when I pulled it out I found it had went into a boot loop again. Once again, I pulled the battery.
But this time, the phone wouldn't power up. I couldn't get it to power up, go into recovery mode, download, anything. Every button combination I tried produced no response. I tried using a different battery, didn't work. I tried charging my phone for a few hours (even though my phone was >75% when this happened) and even the battery indicator screen didn't show when I pressed the home button.
I searched for possible fixes, but I couldn't find any post or thread that was similar enough to the situation I'm in. I'm 99% sure it's not Sudden Death Syndrome, and that's about all I've found.
Anyway, I need help. What can I do (if anything) to make my phone work again?
Click to expand...
Click to collapse
Sounds like SDS, HERES a solution, or if your comfortable soldering, HERE
Follow this guide with the unbrick image pitched in the OP:
http://forum.xda-developers.com/showthread.php?t=2369125
joeyhdownsouth said:
Sounds like SDS, HERES a solution, or if your comfortable soldering, HERE
Click to expand...
Click to collapse
It was my understanding about SDS (and please, by all means correct me if I'm wrong) that a) it only affected phones with firmware below 4.1.2 (and that 4.1.2 and 4.2 had a patch to fix SDS) and b) and it only affected international models, i.e. i9300.