[Q] Symptoms of a bricked phone? (related to all skyrocket users) - AT&T Samsung Galaxy S II Skyrocket SGH-I727

background info:
I am (or was) running MHX superlite 3.0 rom with romracers stockish 0.3 kernel.
UCLA3 modem and radio.
So today my phone decides to restart itself and never will load past the "first two"
samsung screens.
Once these "two" samsung logos pass by, the screen turns blank (not on)
and starts to vibrate with 1 second intervals.
The only way for it to stop is if I pull the battery.
Heres the weird part.
I tried to ODIN back to stock...once I put my phone into DOWNLOAD MODE.
The little android guy that says DOWNLOADING "dont turn off" will show for a millisecond and then the screen will shut off and start the vibrations. ODIN will not recognize the device either
So what I have is a phone that wont load past the samsung logos if the power button is pressed
AND
Download mode works, but the screen will turn blank and vibrations start buzzing.
My phone is having seizures. The only way to stop the vibrations is by pulling the battery.
I have accepted the fact that the phone may be done for.
It was a great 4 months together. tear*

Well, if you can't get it sorted out there's always this! Unless the hardware is busted, but maybe he can fix that too??
http://www.youtube.com/watch?v=AkJQAbwZjRk

Did you try booting into recovery mode instead of odin?

Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.

silver03wrx said:
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
Click to expand...
Click to collapse
No, its not. Can't OC or UV. It can only UC.
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3

if u can boot into cwm flash darkside

OP... what rom/kernel/modem were you running before MHX-SuperLite? and what wipe process did you use prior to MHX flash?

Can you get into recovery and restore a backup?
If you don't have a backup and can get into recovery, try wiping data/cache, then go into mounts/storage and format system, data, and cache, then go to advanced and wipe Dalvic cache. Then power down and try to Odin back to stock again.
If this doesn't work, try another data cable or usb port on your machine (or another pc if this doesn't work). Maybe communication is getting lost due to bad usb connection...
EDIT: Are you saying you tried to Odin even though Odin wasn't recognizing your phone? That could be part of the problem. Try re-installing the Samsung drivers and see if Odin sees it then.
If you can get into download mode you aren't hard bricked yet...

I think he is saying that Odin recognizes his phone but his phone goes black before he can't start the reflash right?
Sent from my SAMSUNG-SGH-I727

Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.

Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts

DoctorQMM said:
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Click to expand...
Click to collapse
MHX is great. The rom has nothing to do with it i believe

Jooosty said:
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
Click to expand...
Click to collapse
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!

skrambled said:
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
Click to expand...
Click to collapse
He already said Odin/connection isn't the problem. His phone won't stay on long enough for the communication to be made. According to what he said, it has nothing to do with machine/drivers/cable. He needs a way of keep the phone on long enough to make the connection, or somehow communicate with it another way. Unfortunately, I have no ideas. Although, I really hope someone does. That RussianBear guy seems to be onto something with communicating with the emmc without the phone being on... or something like that.

heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/

Jooosty said:
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Click to expand...
Click to collapse
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.

plwalsh88 said:
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
Click to expand...
Click to collapse
Or even a external battery charger maybe there is just enough juice to turn on and then dies
Sent from my SAMSUNG-SGH-I727

The battery is fine. Wouldnt keep rebooting if otherwise. O well.
Just bought a captivate to feed my android in me
Sent from my SAMSUNG-SGH-I897 using XDA

DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litmus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....

xtechx said:
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litinus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
Click to expand...
Click to collapse
What ROM were you on man?
Sent from SKYROCKET
NexusMod 4.0
Faux 010m

Related

What the hell did i do?

Okay, so i had Infused 2.3.0 (i think that was the number, it's the latest one anyway). I followed the instructions to the T. I had no issues.
About 3 or 4 days later i woke up and my phone had 1% battery. I sent a text, and then locked the phone. I came back to plug it in, and tried to see if it had any battery. None, it was dead. No biggie. I plug it in, and i get the circle loading thing. Then the battery symbol appears (charging). Then the phone goes black and the circle loading thing appears again. Then it keeps restarting. and going back to the circle loading thing. Over... and Over... Then i tried charging it for a while to see if the battery was just really low. No dice.
I put my girlfriends battery from her infuse 4g and it had 90%. Did the same thing. Circle loading thing, restart, circle loading thing, etc. Then i tried to put it into recovery. No dice, it would just keep restarting. Sometimes the Samsung logo would appear, and then it would just restart samsung, black screen, samsung, black screen, then eventually back to the circle.
I got it in red recovery ONCE, i was able to scroll down twice, and then the phone restarted. I couldn't get it back into red recovery.
I thought i had bricked my phone somehow. So i tried to use GTGs unbrick. I loaded it up fine (i'd done it with my girlfriends phone before to restore it to stock). It took me about 15 tries to get it into download mode. It was in download mode for long enough so that the program recognized it, and it started the download to restore it, then the phone turned off.
Now the phone won't even turn on. I can't put it in download mode, i can't put it into recovery, i can't get it to do ANYTHING.
What the hell did i do? What caused the original issue?
HELP
Does your phone still have warranty?
What the hell didn't you do.
Ok well first of all it is not Infused 2.3 it is 2.2.3. Anyway that is not the point, did you have juice defender installed? I do not think it could have done anything, but maybe. What is the latest app/tweak/anything you installed? Finally, have you tried holding both volume buttons and power button when trying to turn it on? This problem you are having seems extremely odd. Try plugging it in.
eatjello said:
Okay, so i had Infused 2.3.0 (i think that was the number, it's the latest one anyway). I followed the instructions to the T. I had no issues.
About 3 or 4 days later i woke up and my phone had 1% battery. I sent a text, and then locked the phone. I came back to plug it in, and tried to see if it had any battery. None, it was dead. No biggie. I plug it in, and i get the circle loading thing. Then the battery symbol appears (charging). Then the phone goes black and the circle loading thing appears again. Then it keeps restarting. and going back to the circle loading thing. Over... and Over... Then i tried charging it for a while to see if the battery was just really low. No dice.
I put my girlfriends battery from her infuse 4g and it had 90%. Did the same thing. Circle loading thing, restart, circle loading thing, etc. Then i tried to put it into recovery. No dice, it would just keep restarting. Sometimes the Samsung logo would appear, and then it would just restart samsung, black screen, samsung, black screen, then eventually back to the circle.
I got it in red recovery ONCE, i was able to scroll down twice, and then the phone restarted. I couldn't get it back into red recovery.
I thought i had bricked my phone somehow. So i tried to use GTGs unbrick. I loaded it up fine (i'd done it with my girlfriends phone before to restore it to stock). It took me about 15 tries to get it into download mode. It was in download mode for long enough so that the program recognized it, and it started the download to restore it, then the phone turned off.
Now the phone won't even turn on. I can't put it in download mode, i can't put it into recovery, i can't get it to do ANYTHING.
What the hell did i do? What caused the original issue?
HELP
Click to expand...
Click to collapse
Did you try your girlfriend's charged battery with the charger disconnected?
Sarius24 said:
Does your phone still have warranty?
Click to expand...
Click to collapse
Yeah I'm going to try to take it to the ATT store tomorrow to see what they say.
Eddie Bombay said:
What the hell didn't you do.
Click to expand...
Click to collapse
Thank you for the valuable contribution.
Ryanscool said:
Ok well first of all it is not Infused 2.3 it is 2.2.3. Anyway that is not the point, did you have juice defender installed? I do not think it could have done anything, but maybe. What is the latest app/tweak/anything you installed? Finally, have you tried holding both volume buttons and power button when trying to turn it on? This problem you are having seems extremely odd. Try plugging it in.
Click to expand...
Click to collapse
2.2.3, thanks. I was too lazy to look it up. No, I didn't have juice defender. I used Lookout, that's all.
The latest thing I installed was the 2.2.3 update for Infused. I updated Pandora, and that's all.
Yes, i've done that with the volume buttons.
Entropy512 said:
Did you try your girlfriend's charged battery with the charger disconnected?
Click to expand...
Click to collapse
Yes. Won't turn on.
Well, best thing you can do now is see what ATT can do about it. The worst that can happen is they say they can not do anything, which you then can keep trying the ultimate unbrick over again. This helped someone on an earlier thread.
Same thing happened to me. Take the battery out. Make sure USB cable is unplugged. Hold down both up and down volume buttons plug in USB into ur phone and PC and put battery back in. This will put you in download mode and it will stick do u can return to stock. Good luck
Sent from my SAMSUNG-SGH-I997 using XDA App
jmatt78 said:
Same thing happened to me. Take the battery out. Make sure USB cable is unplugged. Hold down both up and down volume buttons plug in USB into ur phone and PC and put battery back in. This will put you in download mode and it will stick do u can return to stock. Good luck
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
I'll try this again, but it didn't work last time. No matter what i did.
EDIT:
Tried again multiple times. It just won't turn on.
I think you have a hardware failure of some sort... Take it back to AT&T for warrany service.
You probably didn't do anything to it - just bad luck and coincidence.
Entropy512 said:
I think you have a hardware failure of some sort... Take it back to AT&T for warrany service.
You probably didn't do anything to it - just bad luck and coincidence.
Click to expand...
Click to collapse
this is exactly what i thought. and what i'm hoping. I'll let you guys know what happens tomorrow at ATT.
let me know what ATT says and how your approach was to them.
I just got my phonw into a boot loop ...
Was thinking if nothing works just play dumb with ATT.
Evanescense said:
let me know what ATT says and how your approach was to them.
I just got my phonw into a boot loop ...
Was thinking if nothing works just play dumb with ATT.
Click to expand...
Click to collapse
I'm at att right now waiting. Ill let you know what I say and what happens.
What rom were you using?
They're replacing it. No questions asked. The phone wont turn on. So they said its a hardware failure
The guy was really nice. Didn't ask me if I did anything to it
He tried everything I did. Download mode. New battery. Nadda
got my replacement today. all is well. now to root

Emancipation boot loop

Running Emancipation A1 for weeks now. Love it. Runs smooth, support is top notch. All of a sudden, I'm stuck at the Samsung logo boot loop. I can't even get into CWM recovery mode to wipe and reflash. Didn't download or change any settings.
Downloading necessary files to go back to stock. In the meantime, if anybody has any suggestions, I'm all ears. Going to be a long night I guess.
If you used a crt on mod, the last 5-10 pages on the main Eman thread may address this problem.
Thanks. No, I didn't install the CRT on mod that was provided. Very strange, because the rom has been running flawless for quite some time. I'm downloading the Heimdall one click file now.
A little nervous at this point. Yes, I've flashed a few Rom's, and flashed a few modems, but never had any problems.
Holding volume up and down Anne pore won't get you to recovery?
If that's the case, you might need to get into download mode and start from scratch via heimdal or Odin
Yeah, can't get into recovery holding up/down volume buttons. I downloaded heimdall, and went back to stock. Not I'm experiencing same problem. Phone continuously rebooting. Can't connect or even get into download mode. Also tried a different USB cord, just to make sure. No difference.
Yikes.
Well this pretty much sucks. I think I went back to stock. The phone booted up briefly enough for me to go into settings and see that it was running a stock version of the software. What it was I can't remember. Probably 2.3.6 just like the post says it will revert to. However, I cannot do anything when I power on now. The phone is stuck in at the Samsung logo and will just flash and flash and flash. Can't get into recovery or download mode. Nothing.
Lavman72 said:
Well this pretty much sucks. I think I went back to stock. The phone booted up briefly enough for me to go into settings and see that it was running a stock version of the software. What it was I can't remember. Probably 2.3.6 just like the post says it will revert to. However, I cannot do anything when I power on now. The phone is stuck in at the Samsung logo and will just flash and flash and flash. Can't get into recovery or download mode. Nothing.
Click to expand...
Click to collapse
is the battery charged?
do you have a jig to force a download mode?
may have to go back thru th q/a thread for similar problems...there's quite a few
If its doing that, it could be a hardware issue. Might need to take it in if you are still under warrantee.
qkster said:
is the battery charged?
do you have a jig to force a download mode?
may have to go back thru th q/a thread for similar problems...there's quite a few
Click to expand...
Click to collapse
battery charged. in fact I have a couple batteries charged, just in case.
not sure what you mean by whether I have a jig to force a download mode.
I'll search through the threads. I'm pretty fed up at this point. Also tired, which isn't helping.
NunHugger said:
If its doing that, it could be a hardware issue. Might need to take it in if you are still under warrantee.
Click to expand...
Click to collapse
I got the Infuse the first weekend it came out, which I think was last May. So I think I'm technically under the 1 year warranty. I also have the Insurance on it. Not sure if that will help.
Well, this didn't have a very happy ending. After playing around with the phone last night trying to revert back to Stock, the phone suddenly stopped working. Wouldn't turn on at all. Tried different batteries, different USB cords, nothing. Replacement on it's way from AT&T free of charge (since I was still under warranty). Refurbished no doubt.
Lavman72 said:
Well, this didn't have a very happy ending. After playing around with the phone last night trying to revert back to Stock, the phone suddenly stopped working. Wouldn't turn on at all. Tried different batteries, different USB cords, nothing. Replacement on it's way from AT&T free of charge (since I was still under warranty). Refurbished no doubt.
Click to expand...
Click to collapse
The ending sounds happy to me. This issue could have happened out of your warrantee...that would have been sad. Hope your are back up and running soon.
Yes, it's bittersweet. Because I really had the phone functioning well and looking the way I wanted. But like you said, it was under warranty, so I can't be all that upset. Just trying to make it through the 4-5 days without having a phone.

G2x - overheat, won't reboot

Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks
Xura08 said:
Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks
Click to expand...
Click to collapse
If you don't mind losing your internal sd card data you can try this and then flash the rom again to see if it fixes it.
http://forum.xda-developers.com/showthread.php?t=1590523
Sent from my LG-P999 using XDA
I tried that (Thanks btw!). It formatted everything and sent the files over but it still does the same exact thing.
If I can't put a rom on it will they know I formatted everything? If so, will that void the warranty?
Xura08 said:
I tried that (Thanks btw!). It formatted everything and sent the files over but it still does the same exact thing.
If I can't put a rom on it will they know I formatted everything? If so, will that void the warranty?
Click to expand...
Click to collapse
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA
mansa_noob said:
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Actually most of the time you will be fine if you send in a rooted phone. There was a thread about this.
Sent from my Handheld Portal Device
mansa_noob said:
It seems like you have a stuck vol- button. Can you take a look and try tapping it lightly to see if it would release.
Don't know if they would if you have standard recovery... If you made a nandroid backup I can tell you how to push that... Then they should not be able to tell anything... Otherwise I think cwm is a dead giveaway
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Yes, I forgot about cwm. I can flash stock t-mo recovery on before I send it in. How would I go about pushing a stock rom onto it?
Also, I don't think I have a stuck vol- button. I've messed with it countless times. I suppose I could take the phone apart and see if it's really stuck. Do you have any other advice? As of now the phone only turns on (it displays the LG screen but after about 5 seconds the logo disappears and the touch buttons at the bottom flash and it repeats. ONLY while plugged into a power source, though)
@zlopp - thanks!
Xura08 said:
Yes, I forgot about cwm. I can flash stock t-mo recovery on before I send it in. How would I go about pushing a stock rom onto it?
Also, I don't think I have a stuck vol- button. I've messed with it countless times. I suppose I could take the phone apart and see if it's really stuck. Do you have any other advice? As of now the phone only turns on (it displays the LG screen but after about 5 seconds the logo disappears and the touch buttons at the bottom flash and it repeats. ONLY while plugged into a power source, though)
@zlopp - thanks!
Click to expand...
Click to collapse
You can use the reference link in the batch cleanup op. That one pushes stock 2.3.3. I don't think it is rooted either.
Does your phone boot loop or does it boot back into recovery?
Sent from my LG-P999 using XDA
bootloop. I can't get it to go into recovery. It won't bootloop, or boot at all, unless plugged into a power source. Does that sound like possibly a failed battery? It was taking forever to charge and whatnot a few weeks prior..
Unplug the phone. Plug it into the wall. Hold the battery in the socket, but dont let it touch the copper conntectors. Turn the phone one. It'll show the lg screen. Before it turns itself off, plug the battery in.
let it charge for $15 mins and redo CWM recovery again.
6 month ago one of my friend g2x fried up the main boardduring charge, I have to paid $100 for broken phone to get the main board replaced
Blazing angel said:
Unplug the phone. Plug it into the wall. Hold the battery in the socket, but dont let it touch the copper conntectors. Turn the phone one. It'll show the lg screen. Before it turns itself off, plug the battery in.
Click to expand...
Click to collapse
I can't believe it but it worked! However, once I flashed a rom and loaded it started giving problems. The battery indicator said 999% and the mainboard began getting a lot warmer than usual. Then it shut off. I turned it back on and the LG logo came up for 1 second then the screen flashed (A brief flash full of what looks like artifacts if a videocard were to fry) and it repeated the cycle. It looks like im sending this POS back to t-mobile
Xura08 said:
I can't believe it but it worked! However, once I flashed a rom and loaded it started giving problems. The battery indicator said 999% and the mainboard began getting a lot warmer than usual. Then it shut off. I turned it back on and the LG logo came up for 1 second then the screen flashed (A brief flash full of what looks like artifacts if a videocard were to fry) and it repeated the cycle. It looks like im sending this POS back to t-mobile
Click to expand...
Click to collapse
No problem. I was pulling my hair out when my phone did it too. It took a lot of experimentation to figure it out!
Now, onto the next problem. I suggest you run the g2x nullifier script to clean out anything on the rom. It might be messing with the phone. Then flash something known to be stable!
My phone also did the 999% thing. It was messing up a lot too, but the nullifier fixed it. Try it out
Xura08 said:
Soo.. I overclocked my G2x at 1.2 GHZ running Eaglesblood 4.0.1. A few days later I was charging my phone and it got SUPER hot around the mainboard (the top area). Shortly after it was thrown in a pile of clothes and the battery popped out (oops). It won't turn on now. It recognizes the android recovery on the computer (pwr + up/dwn vol buttons) and I can flash recovery on it but it wont boot up. When i hooked it up to a charger (a wii) it displays the LG logo for about 5 seconds then the touch buttons lights up then it resets. Before today it would only display the LG logo for about .2 seconds then turn off (only when plugged into a computer).
What should I do? Could it be the battery, or did it overheat? Now, what should I do? Should I send in it for warranty (It had problems before anyways) and risk them being able to boot it and see that I OCd and rooted it?
Any help appreciated... Thanks
Click to expand...
Click to collapse
This SAME EXACT thing is happening to me except I had NO issues with the phone before. The battery had died down after a normal day of use, I charged it that night and then I wake up to it not powering on. Then with charger only a continuous bootloop of the white LG logo

random reboots growing more often daily

Well, this is a loaded question, and I've seen it in various other phones' Q&A sections, but nothing comes up that specifically matches this phone.
Has anyone else identified any application(s) that cause the GS3 to spontaneously reboot - to the point if insanity?
I'm already on "Mike's 2nd Galaxy S3" and VerizonWireless was very helpful yesterday (??) and showed me how to do a safe mode start. I haven't seen that posted, so here's the trick: press and hold the power button until the "Samsung" logo appears, then press and hold the volume down button and quickly release the power button. After cogitating for a few minutes, the phone will come up in 'virgin mode', with "SAFE MODE" displayed at the bottom left corner. So I'm told it loads only factory-original programs in that mode, fair enough.
It still rebooted after about five minutes while we were checking things out. So, friendly S-O-a-B had me do a factory reset. :cyclops: That's cool, I have everything backed up with CWM and TiB and screen-shots of the layout, so it was actually trivial to get everything back. Never-the-less, before I could get through the cycle of updating my phone using the Google Market - er - "Play Store" - it rebooted yet again, this time while I was trying to answer the psuedo-random "Customer Satisfaction Survey" phone-call that you get when you have called tech support - sometimes. Call dropped, I felt the little twitch it gives when it warm boots into the quick-load vector and just said "F it!" and called him back and have yet another ("Mike's 3rd Galaxy S3") coming overnight on Monday. I've had squirrelly phones that were "new models" do weird things before, so no big whoop. Maybe "Door #3" will be better. I know #2 worked better until about a week ago than the original unit.
Just in case anyone wonders: flashing the original factory recovery mode forsaking the OC'd core gives no joy...
OK, I'm calmer, back to the original question: has anyone identified any common APK that makes the SGS3 go spastic? I'm thinking - in my case - since I got a reboot in the 'virginal safe mode' boot it's not going to help, but - just checking.
ratledge said:
Well, this is a loaded question, and I've seen it in various other phones' Q&A sections, but nothing comes up that specifically matches this phone.
Has anyone else identified any application(s) that cause the GS3 to spontaneously reboot - to the point if insanity?
I'm already on "Mike's 2nd Galaxy S3" and VerizonWireless was very helpful yesterday (??) and showed me how to do a safe mode start. I haven't seen that posted, so here's the trick: press and hold the power button until the "Samsung" logo appears, then press and hold the volume down button and quickly release the power button. After cogitating for a few minutes, the phone will come up in 'virgin mode', with "SAFE MODE" displayed at the bottom left corner. So I'm told it loads only factory-original programs in that mode, fair enough.
It still rebooted after about five minutes while we were checking things out. So, friendly S-O-a-B had me do a factory reset. :cyclops: That's cool, I have everything backed up with CWM and TiB and screen-shots of the layout, so it was actually trivial to get everything back. Never-the-less, before I could get through the cycle of updating my phone using the Google Market - er - "Play Store" - it rebooted yet again, this time while I was trying to answer the psuedo-random "Customer Satisfaction Survey" phone-call that you get when you have called tech support - sometimes. Call dropped, I felt the little twitch it gives when it warm boots into the quick-load vector and just said "F it!" and called him back and have yet another ("Mike's 3rd Galaxy S3") coming overnight on Monday. I've had squirrelly phones that were "new models" do weird things before, so no big whoop. Maybe "Door #3" will be better. I know #2 worked better until about a week ago than the original unit.
Just in case anyone wonders: flashing the original factory recovery mode forsaking the OC'd core gives no joy...
OK, I'm calmer, back to the original question: has anyone identified any common APK that makes the SGS3 go spastic? I'm thinking - in my case - since I got a reboot in the 'virginal safe mode' boot it's not going to help, but - just checking.
Click to expand...
Click to collapse
Reflash the stock rom via PDA slot in odin, then wipe/data factory reset in stock recovery!
droidstyle said:
Reflash the stock rom via PDA slot in odin, then wipe/data factory reset in stock recovery!
Click to expand...
Click to collapse
Unfortunately I tried that before I called. I'm using "Route66", but - basically stock ROM + root and the Invisiblek OC to 1.89GHz. I tried backing down the OC to 1.80, then 1.75, and finally just undoing it, flashing it back to CWM 6.0.1, but no joy there, either.
ratledge said:
Unfortunately I tried that before I called. I'm using "Route66", but - basically stock ROM + root and the Invisiblek OC to 1.89GHz. I tried backing down the OC to 1.80, then 1.75, and finally just undoing it, flashing it back to CWM 6.0.1, but no joy there, either.
Click to expand...
Click to collapse
does it reboot at the stock clock speed(1.5)? Also, you went back to the stock kernel and it still reboots?
droidstyle said:
does it reboot at the stock clock speed(1.5)? Also, you went back to the stock kernel and it still reboots?
Click to expand...
Click to collapse
Yep, yep, yep... Sure enough, I can flash the stock recovery and it still reboots, doesn't matter what I have in the RECOVERY.IMG
I've already done the factory reset and reprovisioned my phone twice, also. Fortunately unit #3 will be arriving tomorrow shortly after noon (I live so far out in the weeds that even priority overnight usually gets there around 12:30 or 1)...
Ya I would flash that back to one hundred percent stock. That's really the only way your gonna find out if your phone is truly busted or not.
Sent from my SCH-I535 using xda premium
tapatalk keeps force closing on my and once caused a random reboot . My screen goes black and unresponsive for like 30 seconds then says tapatalk stopped responding or something like that. When it rebooted it also went black and unresponsive for like a minute I was about to pull the battery then it booted back up. Not sure if your having a similar issue there are my $.02
Sent from my SCH-I535 using Tapatalk 2
Mark930 said:
tapatalk keeps force closing on my and once caused a random reboot . My screen goes black and unresponsive for like 30 seconds then says tapatalk stopped responding or something like that. When it rebooted it also went black and unresponsive for like a minute I was about to pull the battery then it booted back up. Not sure if your having a similar issue there are my $.02
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I don't have it installed. I do have the XDA app installed, but while I'm working (like right now), I'm not able to use my cell on the network. :angel:
The thing is the new (2nd) one has about 75% of the crap I had on the original one, and I've slowly whittled that down to about 50%, trying to eliminate anything I thought might be questionable. I've not heard one person P&M about any problems running the "Route66" SYSTEM.IMG for root, or I'd go ahead and flash it back, too. Of course - "within the next 5 days" after receiving the 3rd unit, I'll certainly do that to unit #2, and remove all traces of ever having been anywhere but a factory original image, so they don't pop my plastic for $500 or so. I already did that once when I returned the first one.

[Q] ~I'm Guessing SDS?~

So about 2 weeks ago, i rooted my phone and flashed over the nightly version of CWM. Ran fine for about a week, afterwards i noticed a big battery drain. Then started the freezes, and finally the random restarting. During this time, it would commonly get my battery percentage wrong( Ex: It would say 20% but then die. I would turn it back on and it would say 5. Take out the battery, put it back in, and it would say something like 12%.) Yesterday, i had about 20% left, and it just turns off. Wont turn back on. I get home, plug it up, and its in a charging screen boot loop. Plug in-Go to charging screen-Turn off-repeat. It will do that repeatedly, as long as it's plugged in. I've looked it up, and it looks like it's the SDS (Sudden Death Syndrome) and that Samsung can only fix it under warranty. The problem is, I didn't get this through a carrier contract, i bout it basically new online. Any help? Anyone have advice on how to fix it, or what to do?
Bcaraway14 said:
So about 2 weeks ago, i rooted my phone and flashed over the nightly version of CWM. Ran fine for about a week, afterwards i noticed a big battery drain. Then started the freezes, and finally the random restarting. During this time, it would commonly get my battery percentage wrong( Ex: It would say 20% but then die. I would turn it back on and it would say 5. Take out the battery, put it back in, and it would say something like 12%.) Yesterday, i had about 20% left, and it just turns off. Wont turn back on. I get home, plug it up, and its in a charging screen boot loop. Plug in-Go to charging screen-Turn off-repeat. It will do that repeatedly, as long as it's plugged in. I've looked it up, and it looks like it's the SDS (Sudden Death Syndrome) and that Samsung can only fix it under warranty. The problem is, I didn't get this through a carrier contract, i bout it basically new online. Any help? Anyone have advice on how to fix it, or what to do?
Click to expand...
Click to collapse
Can you still boot into download mode?
Doesn't sound like it's dead, but something weird is going on. Anyway, Odin back to stock and see if your problem persists. This could very likely fix it.
If it does still persist, I bet Samsung has a way to track the serial or imei number to tell how old the phone actually is and when it was activated. I'd call them up anyway and see what they can do.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Can you still boot into download mode?
Doesn't sound like it's dead, but something weird is going on. Anyway, Odin back to stock and see if your problem persists. This could very likely fix it.
If it does still persist, I bet Samsung has a way to track the serial or imei number to tell how old the phone actually is and when it was activated. I'd call them up anyway and see what they can do.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I have not tried Download mode, only a regular boot. Should i have an option for a stock install in odin? I had a CWM backup, but it kept getting a bad sum error, so now i no longer have my stock ROM.
Bcaraway14 said:
I have not tried Download mode, only a regular boot. Should i have an option for a stock install in odin? I had a CWM backup, but it kept getting a bad sum error, so now i no longer have my stock ROM.
Click to expand...
Click to collapse
Once you're in download mode all you have to do is flash a tar file of a stock Rom through Odin, it's located in the development stickies.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Once you're in download mode all you have to do is flash a tar file of a stock Rom through Odin, it's located in the development stickies.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Well, i got home, took out my battery held the power button for 30 seconds..and it worked. My luck, right? I dont know how many times i tried that, but now it decides to work. Thanks for the advice, i guess this can be locked now!

Categories

Resources