I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
dubbz84 said:
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
Click to expand...
Click to collapse
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
GiantJay said:
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
Click to expand...
Click to collapse
Well i just placed the battery back in, it started on it's own without my pressing anything again, and i've been timing the last 5 minutes. but it seems like it will stay a black screen indefinitely. unless i remove the back of the phone, or snap it back into place, or any kind of micro impact movements it seems, when I do that it vibrates like it's first being turned on, and shows the samsung screen, then the samsung galaxy s3 screen, then it will go black again.
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
topherk said:
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Not picking it up on adb.
dante32278 said:
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
After the first odin flash i was thinking the same thing. But that's the thing, it won't stay on the download mode screen long enough for me to even try to flash anything else through odin. I'm also noticing when connected to the charger, if i make a slight impact against the phone with my palm, the screen will briefly show the battery icon as if the phone is charging when it is turned off, then the screen will go black again. When it is unplugged, is when it will show the samsung screen, then the samsung galaxy s3 screen, then go black again.
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
To me it sounds like maybe your power button is stuck "down"
If you didn't know, the power button has a fail safe reboot that happens after holding for about 10 seconds. So no matter what, if you phone is frozen or whatever, holding power more than 10s will cause it to reboot. That would also explain why its turning itself on as soon as you pop in the battery.
toolegit said:
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
Click to expand...
Click to collapse
not recently, and if it was ever dropped, it would be in it's case... But i had noticed that while it was in it's power glove case, sometimes i would have to use more than normal pressure on the power button to get the phone to respond. I was wondering if something was stuck, just haven't read anything like that happening to anyone, and when I used the jig the first time the screen stayed on.
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.
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.
Started acting up last week when I noticed it restarted on it's own, but didn't fire back up right away. Instead it went into a reboot cycle for almost an hour (doesn't make it passed the Samsung splash screen). Then it just fixed itself and I was able to access everything as normal.
Once it was going again, I backed up all my info and did a factory reset and proceeded to re-load Jellybean (4.0.2?). Although Kies said I was already up-to-date and didn't do anything.
Anyway, worked fine for a week until yesterday when it went into the continuous reboot cycle, and never fully turned on again.
I have pictures and vids I would like to somehow recover (on phone and not on SD card), but I have no idea how to get the phone to start up. I have removed my SIM and memory card to see if that did anything. Also have done numerous hard resets (pull the battery and lock + vol down combo). It basically just kills the battery as it cycle reboots. Every few minutes, it will fire up again but still doesn't make it past the Samsung splash page. And when the phone is charging, it just doesn't turn on in general and just intermittently vibrates to try to start-up.
Dunno how I would even be able to flash the ROM (newb at this) since the phone doesn't stay on long enough to access the BIOS of the phone. Does this seem like a software or hardware issue? I bought this phone 2nd hand off Craigs about 2 years ago, so no idea if it was a refurb.
Has anyone experienced this and can direct me to somewhere so I can fix it? Or is it a goner and I should just move on to another phone? Any help would be greatly appreciated.
Its likely a stuck power button. Search here or Google for treatments.
Sent from my Moto X cellular telephone...
it sounds like a problem I had once
Galaxy S2 Wont boot anymore
one option was to disassemble teh phone and check the power button , someone recommended I use an eraser to tap the power button and see if that would unlodge it and to my relief that worked. You might want to try that first
Hello friends. recently my galaxy S3 stopped working while it was charging one day. here is what happend when it suddenly stopped working . I picked it up to send a message to a friend on facebook, after that i tossed my phone down on my pillow and i went back to doing what i was doing. about an hour or so went by and i decided to check my phone again to see if my friend replied. it was then i noticed that the phone was off for some reason. i thought that was kind of weird and just figured maybe it glitched out and just turned itself off or something. i attempted to turn the phone on and it did not respond, but for some reason when i shake the phone or something it would turn on. when its plugged into the charger it doesnt show the charging screen either. occasionally the red light at the top left corner of the device will light up like its charging but then it will turn off again and when it does turn on randomly it doesn't go past the samsung S3 screen when it is booting up. The phone is currently rooted as well but i dont think that has anything to do with my current issue. i just took the phone apart right now to check the motherboard to see if anything was wrong with it or maybe it was dirty ect and when i put the phone back together i actually got it to charge for a moment but i couldn't get it to turn on. ive looked up some videos on youtube about this issue but i couldn't find any info really about it.
so to be clear these are the things i have tried
1. tried to boot it into download mode and recovery mode with no luck.
2. checked to see if it was a hardware issue and everything looked ok.
3. swapped batteries still with no luck.
i dug a little deeper after posting this thread and found out my issue could be what is called SDS (sudden death syndrome) the one thing i didnt find out is if im completely screwed and need a new phone or not. i took it down to my local samsung store here in L.A. and they already turned me down because the phone was rooted and they could tell it was because my phone has a different bootup then normal.
so if anyone could help me out that would be awesome and i would be super grateful. thanks in advance
dev-meepo