At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
UPDATE 12/23/2013:
1. I was able to get into Recovery by quickly pressing reboot and reboot into recovery. From here I could get into Download Mode.
2. I first cleared my Dalvik & Cache and reflashed JellyBeans v19, then cleared Dalvik & Cache again. This did no solve any problems.
3. Next I flashed the Stock VRBMF1 Firmware through Odin, which also did not solve any problems.
4. Now I am downloading Root66 and following Hero's guide to unbricking a soft-bricked device.
usatf1290 said:
At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
Click to expand...
Click to collapse
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the response!
I would try to flash stock packages through Odin, but i cant get to download mode. Usb debugging is enabled.
Ill probably send it Verizon when i get back to the states, but I was wondering if i could do anything in the mean time.
Related
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.
I have an AT&T Huawei-U8665 (Fusion 2 go-phone) that I rooted. I did not change out the stock rom or any other tweaks except for allowing root access. After I rooted it (about a week ago), after a few days of use, it started getting stuck in a reboot-loop. I had to reset user data to get it to stop. After another two days of using it, same thing - reboot-loop, reset user data. However, this time when SuperSu asked where to update the binary too, TWRP or normal, I accidentally selected TWRP. The phone rebooted itself but will only go to the first screen (at&t logo) and then turn back off, then back to the first screen, then back off, repeatedly and non-stop.
Things I've tried:
Pulling out the battery (short amount of time, long amount of time), Power + Volume Up, Power + Volume Down. I've even taken the battery out and plugged the phone it - Every single one has the phone go to the at&t logo screen then back off, repeat...
Is there ANYTHING that will fix this???
Please help me if you can! Thanks!!
Quixs said:
I have an AT&T Huawei-U8665 (Fusion 2 go-phone) that I rooted. I did not change out the stock rom or any other tweaks except for allowing root access. After I rooted it (about a week ago), after a few days of use, it started getting stuck in a reboot-loop. I had to reset user data to get it to stop. After another two days of using it, same thing - reboot-loop, reset user data. However, this time when SuperSu asked where to update the binary too, TWRP or normal, I accidentally selected TWRP. The phone rebooted itself but will only go to the first screen (at&t logo) and then turn back off, then back to the first screen, then back off, repeatedly and non-stop.
Things I've tried:
Pulling out the battery (short amount of time, long amount of time), Power + Volume Up, Power + Volume Down. I've even taken the battery out and plugged the phone it - Every single one has the phone go to the at&t logo screen then back off, repeat...
Is there ANYTHING that will fix this???
Please help me if you can! Thanks!!
Click to expand...
Click to collapse
did you try to flash some custom rom or kernel ?
how much battery percentage you have?
sometimes it is due to the less battery power..
try charging your battery using master charger and after the battery is full then try turning your phone on.
if still dont work then try flashing the rom either stock rom or custom.
and which device r u using?
the hellboy said:
did you try to flash some custom rom or kernel ?
how much battery percentage you have?
sometimes it is due to the less battery power..
try charging your battery using master charger and after the battery is full then try turning your phone on.
if still dont work then try flashing the rom either stock rom or custom.
and which device r u using?
Click to expand...
Click to collapse
Thanks for the reply! It wont boot long enough to show the battery symbol, but I always keep my device charged (even though I know it isn't advised). Also, I can't get it into safe or recovery mode, only the purple screen (no matter which one I try). I've tried to use my pc to run fastboot but it just states "waiting on device" and I do have the proper drivers installed as well. I will keep it plugged in all night and try tomorrow. Hopefully it will charge while it flashes the at&t logo on and off. Thanks for the suggestions - I will definitely try again. And, if you think of anything else to try, I will definitely try that too! Oh, and the device is the Huawei-u8665 (at&t Fusion 2 go-phone that runs 2.3.6).
Quixs said:
Thanks for the reply! It wont boot long enough to show the battery symbol, but I always keep my device charged (even though I know it isn't advised). Also, I can't get it into safe or recovery mode, only the purple screen (no matter which one I try). I've tried to use my pc to run fastboot but it just states "waiting on device" and I do have the proper drivers installed as well. I will keep it plugged in all night and try tomorrow. Hopefully it will charge while it flashes the at&t logo on and off. Thanks for the suggestions - I will definitely try again. And, if you think of anything else to try, I will definitely try that too! Oh, and the device is the Huawei-u8665 (at&t Fusion 2 go-phone that runs 2.3.6).
Click to expand...
Click to collapse
ok, BOL:good:
thanks for the help
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!
I have done hours of searches and can't find the answer to my problem. Hopefully someone here can help.
My GT-N8013 is stuck in the Samsung Galaxy Note 10.1 logo screen. I can't even turn it off without it bringing this screen right back up. It only goes dead when I unplug it and let the battery run out of juice.
I can get it to restart into Odin Download mode, but not into the recovery mode. I can install roms and CWM and stock roms using both Kies and desktop Odin3, and I get "pass" status with no errors, most the time, when I do rom update, but I can't get to the restore screen with the power + volume up button, then releasing the power button and holding down the volume up button only. It just stays on the Logo screen.
I hold down the power + Volume down button and it will restart into the Warning screen that allows me to hit the volume down to go to the download screen or volume up to cancel and restart. Both the volume up and down buttons work for this action so I'm sure the buttons are working okay.
I thought maybe the battery wasn't charging right and that was preventing it from going into recovery mode, but I can charge it for a while and unplug it and the screen will stay on the logo screen for a long time, so I think the battery is okey.
Samsung just said I should send it in, but it is out of warranty and I don't want to put much more money into this devices since it is old and a new version is out now, but I hate to think a great device like this that worked so well for so long is now going to be worthless because I can't figure out how to fix it. Hardware seams to be working fine and just a few days ago, the software was working fine. I'm so confused.
Leading up to these events, I had it turned off for a few weeks because I was traveling and going on airplanes and never ended up using it on the trips so it remained turned off. When I turned it back on, there was a OTA system update that I wasn't sure what it did. Didn't appear to do anything noticeable. Still worked normal. Then a few days later I did a personal data wipe because I was going to sell it and get the new Note 10.1. I went through the new setup process without problems, everything was fine. I sold it to a guy and a day later he contacts me and says it isn't working properly and I've been dealing with this ever since. It didn't appear to have any physical damage and the custom binary download count was at "No" so I don't think he tried to load any custom roms. I don't think this guy is tech savvy enough to do anything but plug it in and use it normal, so I don't suspect foul play.
Any help would be greatly appreciated. Thanks.
Check this
http://forum.xda-developers.com/showthread.php?t=2477626
Sent from my GT-N8013 using Tapatalk HD
I have the exact same symptoms. (No recovery mode / stuck on boot screen even after fresh stock rom installed). Out of the blue after working fine the day before.
Anyone know:
a) of anything further that I can try to resurrect this
b) if I might still have any joy getting warranty service from the shop I bought it from in the UK / Samsung if they send it back to them. I have more than a year left on the 2-year warranty they provided, and have only ever run/attempted to run stock. However as I have been out of the UK my custom binary count has increased to 7 as I have tried to reinstall Stock Roms myself to fix the problem. (However OS version still shows as Samsung Official, not custom)
Thanks so much if anyone can help me
Custom binary 7 = warranty void .
I would try flashing Philz recovery tar through Odin and try recovery mode .
So I just picked up this s3, it will turn on but shuts off halfway through galaxy splash screen. Boots into recovery and Odin mode just fine, prior to purchasing we plugged it in, got it to boot and did a factory reset, to clear privious owners data, and it went fine, did it reboot and took me to setup. Satisfied with its performance I went ahead and made the purchase, upon unplugging it shut off, as I expected if battery was indeed shot. What gets me is I let it charge, unplugged, booted, shut off at splash screen, plug back in and says its still fully charged. Boot into recovery and indeed, 100% battery. I haven't gotten around to flashing twrp or rooting, was wondering if anyone has experienced this?
Sent from my HTC Desire HD using XDA Free mobile app
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Phone was already on 4.4 when I got it, I downloaded and flashed stock firmware (ne1) via odin, I got the whole way to the end of setup and as soon as it started loading the homescreen it cut off and went to the green battery charge icon when phones off. Everytime I try and boot it, she'll go through all the splash screens and ill catch a very short glimpse of the homescreen and it shuts off. Also it HAS to be plugged in still, or else it just shuts off halfway through initial "galaxy s3" splash.. I don't understand...
Have you tried a new battery? Even if it's plugged in it won't run if the battery is completely shot.
Also if you indeed have a Verizon S3 on NE1 firmware you will not be able to install TWRP as the bootloader is locked. You will be able to root, however.
Muhff said:
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Click to expand...
Click to collapse
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
XdrummerXboy said:
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Muhff said:
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Click to expand...
Click to collapse
I'm glad you fixed the problem!
Sent from my SCH-I535 using XDA Free mobile app